CVE-2017-9345
UnknownEPSS 3.02%
Last modified
CVE-2017-9345 is a vulnerability of currently unknown severity. In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DNS dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-dns.c by trying to detect self-referencing pointers.. EPSS estimates a 3.02% chance of exploitation in the next 30 days.
Description
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DNS dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-dns.c by trying to detect self-referencing pointers.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | >= 2.0.0, <= 2.0.12 |
| Wireshark | Wireshark | >= 2.2.0, <= 2.2.6 |
References
- http://www.securityfocus.com/bid/98798Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038612Third Party Advisory, VDB Entry
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1206Issue Tracking, Third Party Advisory
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13633Issue Tracking, Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-26.htmlVendor Advisory
- http://www.securityfocus.com/bid/98798Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038612Third Party Advisory, VDB Entry
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1206Issue Tracking, Third Party Advisory
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13633Issue Tracking, Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-26.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-9345?
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DNS dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-dns.c by trying to detect self-referencing pointers.
How severe is CVE-2017-9345?
Severity scoring for CVE-2017-9345 is pending analysis. The EPSS model estimates a 3.02% probability of exploitation in the next 30 days.
How do I fix CVE-2017-9345?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
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-9337The Markdown on Save Improved plugin 2.5 for WordPress has a…
- CVE-2017-9338Inadequate escaping lead to XSS vulnerability in the search …5.4
- CVE-2017-9339A logical error in ownCloud Server before 10.0.2 caused disc…5.3
- CVE-2017-9340An attacker is logged in as a normal user and can somehow ma…6.5
- CVE-2017-9343In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the MSNIP d…
- CVE-2017-9344In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetoo…
- CVE-2017-9346In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the SoulSee…
- CVE-2017-9347In Wireshark 2.2.0 to 2.2.6, the ROS dissector could crash w…
- CVE-2017-9348In Wireshark 2.2.0 to 2.2.6, the DOF dissector could read pa…
- CVE-2017-9349In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DICOM d…
- CVE-2017-9350In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAF…
- CVE-2017-9351In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DHCP di…
Are you affected by CVE-2017-9345?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST