CVE-2017-6474
UnknownEPSS 2.92%
Last modified
CVE-2017-6474 is a vulnerability of currently unknown severity. In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a NetScaler file parser infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by validating record sizes.. EPSS estimates a 2.92% chance of exploitation in the next 30 days.
Description
In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a NetScaler file parser infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by validating record sizes.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | >= 2.0.0, <= 2.0.10 |
| Wireshark | Wireshark | >= 2.2.0, <= 2.2.4 |
| Debian | Debian Linux | 8.0 |
References
- http://www.debian.org/security/2017/dsa-3811Third Party Advisory
- http://www.securityfocus.com/bid/96566Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13429Issue Tracking, Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-07.htmlVendor Advisory
- http://www.debian.org/security/2017/dsa-3811Third Party Advisory
- http://www.securityfocus.com/bid/96566Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13429Issue Tracking, Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-07.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-6474?
In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a NetScaler file parser infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by validating record sizes.
How severe is CVE-2017-6474?
Severity scoring for CVE-2017-6474 is pending analysis. The EPSS model estimates a 2.92% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6474?
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-6468In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a …
- CVE-2017-6469In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is an…
- CVE-2017-6470In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is an…
- CVE-2017-6471In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a …
- CVE-2017-6472In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is an…
- CVE-2017-6473In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a …
- CVE-2017-6478paintballrefjosh/MaNGOSWebV4 before 4.0.8 is vulnerable to a…6.1
- CVE-2017-6479FenixHosting/fenix-open-source before 2017-03-04 is vulnerab…
- CVE-2017-6480groovel/cmsgroovel before 3.3.7-beta is vulnerable to a refl…
- CVE-2017-6481Multiple Cross-Site Scripting (XSS) issues were discovered i…
- CVE-2017-6482Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-6483Multiple Cross-Site Scripting (XSS) issues were discovered i…
Are you affected by CVE-2017-6474?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST