Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Change-Id: Ib2ce6fe0c63523943f1fe7d772010824fe2c0d41
|
|
Change-Id: I3cc0d412048588389bb26e10136fe244bd6b09ed
|
|
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
|
|
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
|
|
Change-Id: Ib989aba05e22b252cdc1c5cd0833d7b12148834f
|
|
Change-Id: I1d967beabf142004da43eefd75aaad22b91d7f11
Signed-off-by: Taesoo Jun <steve.jun@samsung.com>
|
|
Change-Id: Ica75171d1fca20658d00ddbf78a5c1d6239c619c
Signed-off-by: Saurav Babu <saurav.babu@samsung.com>
|
|
Change-Id: I490892f19c71ba126fa4e1d3d78e730429a3b454
|
|
Change-Id: I675ce6dbc5f34403b8acb058f5db60bdff22d059
|
|
Change-Id: If42cd52f40125778f16f4fd58d215f9959555818
Signed-off-by: Taesub Kim <taesub.kim@samsung.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|