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 |
---|---|
http://www.securityfocus.com/bid/97633 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1038262 | |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13477 | Issue Tracking Patch |
https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=2f322f66cbcca2fefdaa630494f9d6c97eb659b7 | |
https://security.gentoo.org/glsa/201706-12 | |
https://www.wireshark.org/security/wnpa-sec-2017-13.html | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
07 Nov 2023, 02:50
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2017-04-12 23:59
Updated : 2024-02-28 15:44
NVD link : CVE-2017-7702
Mitre link : CVE-2017-7702
CVE.ORG link : CVE-2017-7702
JSON object : View
Products Affected
wireshark
- wireshark
CWE
CWE-835
Loop with Unreachable Exit Condition ('Infinite Loop')