In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow.
References
Link | Resource |
---|---|
https://www.wireshark.org/security/wnpa-sec-2017-01.html | Vendor Advisory |
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=781f03580c81339513bb1238b202b72469a1240b | Patch Vendor Advisory |
https://code.wireshark.org/review/#/c/19746/ | Patch Vendor Advisory |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13344 | Issue Tracking Patch Third Party Advisory VDB Entry |
http://www.securityfocus.com/bid/95795 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1037694 | |
http://www.debian.org/security/2017/dsa-3811 |
Configurations
Configuration 1 (hide)
|
Information
Published : 2017-01-25 13:59
Updated : 2019-10-02 17:03
NVD link : CVE-2017-5596
Mitre link : CVE-2017-5596
JSON object : View
CWE
Products Affected
wireshark
- wireshark