Vulnerability Description
In Wireshark through 2.0.13 and 2.2.x through 2.2.7, 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 validation of the relationships between indexes and lengths. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-7702.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | 2.0.0 |
Related Weaknesses (CWE)
References
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13796Issue TrackingPatchVendor Advisory
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=3c7168cc
- https://www.wireshark.org/security/wnpa-sec-2017-13.htmlVendor Advisory
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13796Issue TrackingPatchVendor Advisory
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=3c7168cc
- https://www.wireshark.org/security/wnpa-sec-2017-13.htmlVendor Advisory
FAQ
What is CVE-2017-11410?
CVE-2017-11410 is a vulnerability with a CVSS score of 7.5 (HIGH). In Wireshark through 2.0.13 and 2.2.x through 2.2.7, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissector...
How severe is CVE-2017-11410?
CVE-2017-11410 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2017-11410?
Check the references section above for vendor advisories and patch information. Affected products include: Wireshark Wireshark.