Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1419074

Summary: CVE-2016-7929 tcpdump: Buffer overflow in Juniper PPPoE ATM parser in print-juniper.c:juniper_parse_header()
Product: [Other] Security Response Reporter: Adam Mariš <amaris>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: luhliari, mruprich, msehnout, msekleta, thozza
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tcpdump 4.9.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-20 03:49:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1419114    
Bug Blocks:    

Description Adam Mariš 2017-02-03 15:16:44 UTC 
Buffer overflow in Juniper PPPoE ATM parser in print-juniper.c:juniper_parse_header() was found that may cause a segmentation fault. This issue can be be exploited either locally by making the target system to decode crafted .pcap file using tcpdump, or remotely by sending crafted packets to the network segment where the target system is running tcpdump decoding the live packet capture.

Upstream changelog:

http://www.tcpdump.org/tcpdump-changes.txt
Comment 1 Adam Mariš 2017-02-03 15:16:56 UTC 
Acknowledgments:

Name: the Tcpdump project
Comment 2 Adam Mariš 2017-02-03 15:36:12 UTC 
Created tcpdump tracking bugs for this issue:

Affects: fedora-all [bug 1419114]
Comment 3 Doran Moppert 2017-02-20 03:49:15 UTC 

*** This bug has been marked as a duplicate of bug 1419066 ***