CVE-2017-9345
First published: Fri Jun 02 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Wireshark Wireshark | >=2.0.0<=2.0.12 | |
| Wireshark Wireshark | >=2.2.0<=2.2.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/98798
- http://www.securitytracker.com/id/1038612
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1206
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13633
- https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=e280c9b637327a65d132bfe72d917b87e6844eb5
- https://www.wireshark.org/security/wnpa-sec-2017-26.html
Frequently Asked Questions
What is the severity of CVE-2017-9345?
The severity of CVE-2017-9345 is considered medium due to the potential for an infinite loop in the DNS dissector.
How do I fix CVE-2017-9345?
To fix CVE-2017-9345, update Wireshark to version 2.2.7 or later, or to version 2.0.13 or later.
What versions of Wireshark are affected by CVE-2017-9345?
CVE-2017-9345 affects Wireshark versions from 2.0.0 to 2.0.12 and from 2.2.0 to 2.2.6.
What type of vulnerability is CVE-2017-9345?
CVE-2017-9345 is a denial of service vulnerability due to an infinite loop in the DNS dissector.
Can CVE-2017-9345 be exploited remotely?
Yes, CVE-2017-9345 can potentially be exploited remotely through malicious DNS packets.
- collector/nvd-index
- agent/severity
- agent/weakness
- agent/author
- vendor/wireshark
- canonical/wireshark wireshark
- version/wireshark wireshark/2.0.0
- version/wireshark wireshark/2.0.12
- version/wireshark wireshark/2.2.0
- version/wireshark wireshark/2.2.6