CVE-2017-6469
Last modified
CVE-2017-6469 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 an LDSS dissector crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-ldss.c by ensuring that memory is allocated for a certain data structure.. 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 an LDSS dissector crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-ldss.c by ensuring that memory is allocated for a certain data structure.
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/96577Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13346Issue Tracking, Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-03.htmlVendor Advisory
- http://www.debian.org/security/2017/dsa-3811Third Party Advisory
- http://www.securityfocus.com/bid/96577Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13346Issue Tracking, Patch, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2017-03.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-6469?
How severe is CVE-2017-6469?
How do I fix CVE-2017-6469?
Are you affected by CVE-2017-6469?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
