CVE-2018-14367
UnknownEPSS 3.32%
Last modified
CVE-2018-14367 is a vulnerability of currently unknown severity. In Wireshark 2.6.0 to 2.6.1 and 2.4.0 to 2.4.7, the CoAP protocol dissector could crash. This was addressed in epan/dissectors/packet-coap.c by properly checking for a NULL condition.. EPSS estimates a 3.32% chance of exploitation in the next 30 days.
Description
In Wireshark 2.6.0 to 2.6.1 and 2.4.0 to 2.4.7, the CoAP protocol dissector could crash. This was addressed in epan/dissectors/packet-coap.c by properly checking for a NULL condition.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wireshark | Wireshark | >= 2.4.0, <= 2.4.7 |
| Wireshark | Wireshark | >= 2.6.0, <= 2.6.1 |
References
- http://www.securityfocus.com/bid/104847Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1041608Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14966Issue Tracking, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2018-42.htmlVendor Advisory
- http://www.securityfocus.com/bid/104847Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1041608Third Party Advisory, VDB Entry
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14966Issue Tracking, Vendor Advisory
- https://www.wireshark.org/security/wnpa-sec-2018-42.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-14367?
In Wireshark 2.6.0 to 2.6.1 and 2.4.0 to 2.4.7, the CoAP protocol dissector could crash. This was addressed in epan/dissectors/packet-coap.c by properly checking for a NULL condition.
How severe is CVE-2018-14367?
Severity scoring for CVE-2018-14367 is pending analysis. The EPSS model estimates a 3.32% probability of exploitation in the next 30 days.
How do I fix CVE-2018-14367?
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 2018
- CVE-2018-14360An issue was discovered in NeoMutt before 2018-07-16. nntp_a…9.8
- CVE-2018-14361An issue was discovered in NeoMutt before 2018-07-16. nntp.c…9.8
- CVE-2018-14362An issue was discovered in Mutt before 1.10.1 and NeoMutt be…9.8
- CVE-2018-14363An issue was discovered in NeoMutt before 2018-07-16. newsrc…7.5
- CVE-2018-14364GitLab Community and Enterprise Edition before 10.7.7, 10.8.…
- CVE-2018-14366download.cgi in Pulse Secure Pulse Connect Secure 8.1RX befo…
- CVE-2018-14368In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.…
- CVE-2018-14369In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.…
- CVE-2018-1437IBM Notes 8.5 and 9.0 could allow an attacker to execute arb…7.8
- CVE-2018-14370In Wireshark 2.6.0 to 2.6.1 and 2.4.0 to 2.4.7, the IEEE 802…
- CVE-2018-14371The getLocalePrefix function in ResourceManager.java in Ecli…
- CVE-2018-14373Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
Are you affected by CVE-2018-14367?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST