CVE-2017-9353
UnknownEPSS 14.01%
Last modified
CVE-2017-9353 is a vulnerability of currently unknown severity. In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address.. EPSS estimates a 14.01% chance of exploitation in the next 30 days.
Description
In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | >= 2.2.0, <= 2.2.6 |
References
- http://www.securityfocus.com/bid/98805Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038612Third Party Advisory, VDB Entry
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1303Issue Tracking, Third Party Advisory
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13675Issue Tracking, Patch, Vendor Advisory
- https://www.exploit-db.com/exploits/42123/Exploit, Third Party Advisory, VDB Entry
- https://www.wireshark.org/security/wnpa-sec-2017-33.htmlVendor Advisory
- http://www.securityfocus.com/bid/98805Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038612Third Party Advisory, VDB Entry
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1303Issue Tracking, Third Party Advisory
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13675Issue Tracking, Patch, Vendor Advisory
- https://www.exploit-db.com/exploits/42123/Exploit, Third Party Advisory, VDB Entry
- https://www.wireshark.org/security/wnpa-sec-2017-33.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-9353?
In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address.
How severe is CVE-2017-9353?
Severity scoring for CVE-2017-9353 is pending analysis. The EPSS model estimates a 14.01% probability of exploitation in the next 30 days.
How do I fix CVE-2017-9353?
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-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…
- CVE-2017-9352In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bazaar …
- CVE-2017-9354In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the RGMP di…
- CVE-2017-9355XML external entity (XXE) vulnerability in the import playli…
- CVE-2017-9356Sitecore.NET 7.1 through 7.2 has a Cross Site Scripting Vuln…
- CVE-2017-9358A memory exhaustion vulnerability exists in Asterisk Open So…
- CVE-2017-9359The multi-part body parser in PJSIP, as used in Asterisk Ope…
- CVE-2017-9360WebsiteBaker v2.10.0 has a SQL injection vulnerability in /a…
Are you affected by CVE-2017-9353?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST