Buffer over-read in print-juniper.c:juniper_parse_header() in Juniper protocols parser was found.
This vulnerability can be exploited in two ways. The first is to produce a .pcap file with crafted packet(s) for the protocol(s) concerned and make the target system try to decode the file using tcpdump. The second is to send specially crafted packet(s) to the network segment where the target system is running a tcpdump process that is decoding a live packet capture. In the latter case it depends on the specific network protocol if the crafted packet(s) may be sent from the local segment only or from a remote Internet host.
Name: the Tcpdump project
One external reference should be added :
When we do fuzzing, we generate one simple testcase which makes AddressSanitizer to detect buffer overflow in line 1318 of print-juniper.c (https://github.com/the-tcpdump-group/tcpdump/commit/b534e304568585707c4a92422aeca25cf908ff02#diff-67c6ce093edba0afa3de6b2a04cd2cceR1318)
Sorry for the spam. I mixed it with CVE-2017-12993(https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12993)
This issue was addressed in Red Hat Enterprise Linux 7 via RHEA-2018:0705, which rebased tcpdump to 4.9.2: