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?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-5590An incorrect implementation of "XEP-0280: Message Carbons" i…
- CVE-2017-5591An incorrect implementation of "XEP-0280: Message Carbons" i…5.9
- CVE-2017-5592An incorrect implementation of "XEP-0280: Message Carbons" i…5.9
- CVE-2017-5593An incorrect implementation of "XEP-0280: Message Carbons" i…
- CVE-2017-5594An issue was discovered in Pagekit CMS before 1.0.11. In thi…7.5
- CVE-2017-5595A file disclosure and inclusion vulnerability exists in web/…
- CVE-2017-5597In Wireshark 2.2.0 to 2.2.3 and 2.0.0 to 2.0.9, the DHCPv6 d…
- CVE-2017-5598An issue was discovered in eClinicalWorks healow@work 8.0 bu…
- CVE-2017-5599An issue was discovered in eClinicalWorks Patient Portal 7.0…
- CVE-2017-5600The Data Warehouse component in NetApp OnCommand Insight bef…
- CVE-2017-5601An error in the lha_read_file_header_1() function (archive_r…
- CVE-2017-5602An incorrect implementation of "XEP-0280: Message Carbons" i…
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
