PPP: When un-escaping, don't allocate a too-large buffer.
The buffer should be big enough to hold the captured data, but it
doesn't need to be big enough to hold the entire on-the-network packet,
if we haven't captured all of it.
(backported from commit
e4add0b010ed6f2180dcb05a13026242ed935334)
CVE-2020-8037
Change-Id: Ic28093fcb75e2c597aa8486bf81427fa244694a2
If decode_prefix6() returns a negative number, don't print buf.
If it returns a negative number, it hasn't necessarily filled in buf, so
just return immediately; this is similar to the IPv4 code path, wherein
we just return a negative number, and print nothing, on an error.
This should fix GitHub issue #763.
CVE-2018-19519, CVE-2019-1010220
https://github.com/the-tcpdump-group/tcpdump/commit/
511915bef7e4de2f31b8d9f581b4a44b0cfbcf53
Change-Id: I50c0b4bc2254917b19f5e1432a8242cb76a72237
CVE-2017-16808/AoE: Add a missing bounds check.
In aoev1_reserve_print() check bounds before trying to print an Ethernet
address.
Updated from a Denis Ovsienko's fix.
This fixes a buffer over-read discovered by Bhargava Shastry,
SecT/TU Berlin.
https://github.com/the-tcpdump-group/tcpdump/commit/
28f610026d901660dd370862b62ec328727446a2?diff=split
Change-Id: I8d6cbde6e93809124a16fc94d3707ec64bf4417e
projects / platform / upstream / tcpdump.git / log