In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation.
References
Link | Resource |
---|---|
https://www.wireshark.org/security/wnpa-sec-2017-13.html | Vendor Advisory |
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=2f322f66cbcca2fefdaa630494f9d6c97eb659b7 | Issue Tracking Patch Vendor Advisory |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477 | Issue Tracking Patch |
http://www.securityfocus.com/bid/97633 | Third Party Advisory VDB Entry |
https://security.gentoo.org/glsa/201706-12 | |
http://www.securitytracker.com/id/1038262 |
Configurations
Configuration 1 (hide)
|
Information
Published : 2017-04-12 16:59
Updated : 2019-10-02 17:03
NVD link : CVE-2017-7702
Mitre link : CVE-2017-7702
JSON object : View
CWE
CWE-835
Loop with Unreachable Exit Condition ('Infinite Loop')
Products Affected
wireshark
- wireshark