Greetings. Recently an independent researcher had discovered a vulnerability in tcpdump, which would be a segmentation fault triggered through feeding into tcpdump a crafted packet, either from a live network interface or from a .pcap file. It has been assigned CVE-2015-3138 and you can find the steps to reproduce it here: https://github.com/the-tcpdump-group/tcpdump/issues/446 Subsequent analysis made it clear that the vulnerability was introduced into one of tcpdump functions by an accident not long before the 4.7.0 release. It remained in tcpdump releases 4.7.2 and 4.7.3 (4.7.1 was never released). The next release, 4.7.4, will have it fixed, but it is likely to be delayed. Since the vulnerability has been public for a few weeks, meanwhile you might want to fix it in an update to the tcpdump package. The fix is in the following commit: https://github.com/the-tcpdump-group/tcpdump/commit/3ed82f4ed0095768529afc22b923c8f7171fff70 Let me know if you need any additional information about this case. Reproducible: Always
Upon a closer look this does not seem to affect the current stable version, 4.6.2-r1, as such reducing whiteboard to ~3
FYI, 4.7.4 is in the tree, and the vulnerable 4.7.3 has been removed.
(In reply to Jeroen Roovers from comment #2) > FYI, 4.7.4 is in the tree, and the vulnerable 4.7.3 has been removed. Thank you. Closing noglsa for ~arch only.
