Date: Mon, 01 Apr 2024 07:50:38 +0000 From: bugzilla-noreply@freebsd.org To: pf@FreeBSD.org Subject: [Bug 278034] tcpdump's ip6_print can read beyond buffer end Message-ID: <bug-278034-16861-Oxr3hO0ClN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278034-16861@https.bugs.freebsd.org/bugzilla/> References: <bug-278034-16861@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278034 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kp@freebsd.org --- Comment #2 from Kristof Provost <kp@freebsd.org> --- I'm not terribly familiar with the way tcpdump handles packet parsing. Is the issue here that ip6_print() passes the wrong length value, or that pfsync_print() misinterprets the passed length, and ought to be using acces= sor functions like GET_BE_U_2() and friends which do check the actual data leng= th? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278034-16861-Oxr3hO0ClN>