CVE-2017-5596
Last modified
CVE-2017-5596 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.90% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | 2.0.0 |
| Wireshark | Wireshark | 2.0.1 |
| Wireshark | Wireshark | 2.0.2 |
| Wireshark | Wireshark | 2.0.3 |
| Wireshark | Wireshark | 2.0.4 |
| Wireshark | Wireshark | 2.0.5 |
| Wireshark | Wireshark | 2.0.6 |
| Wireshark | Wireshark | 2.0.7 |
| Wireshark | Wireshark | 2.0.8 |
| Wireshark | Wireshark | 2.0.9 |
| Wireshark | Wireshark | 2.2.0 |
| Wireshark | Wireshark | 2.2.1 |
| Wireshark | Wireshark | 2.2.2 |
| Wireshark | Wireshark | 2.2.3 |
References
- http://www.securityfocus.com/bid/95795Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13344Issue Tracking, Patch, Third Party Advisory, VDB Entry
- https://code.wireshark.org/review/#/c/19746/Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-01.htmlVendor Advisory
- http://www.securityfocus.com/bid/95795Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13344Issue Tracking, Patch, Third Party Advisory, VDB Entry
- https://code.wireshark.org/review/#/c/19746/Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-01.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5596?
How severe is CVE-2017-5596?
How do I fix CVE-2017-5596?
Are you affected by CVE-2017-5596?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
