CVE-2016-9375
Last modified
CVE-2016-9375 is a vulnerability of currently unknown severity. In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the DTN dissector could go into an infinite loop, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dtn.c by checking whether SDNV evaluation was successful.. EPSS estimates a 1.58% chance of exploitation in the next 30 days.
Description
In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the DTN dissector could go into an infinite loop, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dtn.c by checking whether SDNV evaluation was successful.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | 2.0.0 |
| Wireshark | Wireshark | 2.0.1 |
| Wireshark | Wireshark | 2.0.2 |
| Wireshark | Wireshark | 2.0.3 |
| Wireshark | Wireshark | 2.0.4 |
| Wireshark | Wireshark | 2.0.5 |
| Wireshark | Wireshark | 2.0.6 |
| Wireshark | Wireshark | 2.0.7 |
| Wireshark | Wireshark | 2.2.0 |
| Wireshark | Wireshark | 2.2.1 |
| Debian | Debian Linux | 8.0 |
References
- http://www.debian.org/security/2016/dsa-3719Third Party Advisory
- http://www.securityfocus.com/bid/94369Third Party Advisory, VDB Entry
- https://www.wireshark.org/security/wnpa-sec-2016-62.htmlVendor Advisory
- http://www.debian.org/security/2016/dsa-3719Third Party Advisory
- http://www.securityfocus.com/bid/94369Third Party Advisory, VDB Entry
- https://www.wireshark.org/security/wnpa-sec-2016-62.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-9375?
How severe is CVE-2016-9375?
How do I fix CVE-2016-9375?
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 2016
- CVE-2016-9369An issue was discovered in Moxa NPort 5110 versions prior to…9.8
- CVE-2016-9370Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-9371An issue was discovered in Moxa NPort 5110 versions prior to…
- CVE-2016-9372In Wireshark 2.2.0 to 2.2.1, the Profinet I/O dissector coul…
- CVE-2016-9373In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the DCERPC d…
- CVE-2016-9374In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the AllJoyn …
- CVE-2016-9376In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the OpenFlow…
- CVE-2016-9377Xen 4.5.x through 4.7.x on AMD systems without the NRip feat…
- CVE-2016-9378Xen 4.5.x through 4.7.x on AMD systems without the NRip feat…
- CVE-2016-9379The pygrub boot loader emulator in Xen, when S-expression ou…
- CVE-2016-9380The pygrub boot loader emulator in Xen, when nul-delimited o…
- CVE-2016-9381Race condition in QEMU in Xen allows local x86 HVM guest OS …7.5
Are you affected by CVE-2016-9375?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
