Security readout for executives and security teams
Plain-English summary
This CVE affects Wireshark versions that can crash while dissecting IEEE 802.15.4 traffic. The business impact is mainly interruption of packet analysis workflows, not a confirmed system compromise. Sources do not provide a CVSS score or evidence of active exploitation.
Executive priority
Treat this as a targeted availability risk for security operations and network analysis teams. It should be remediated through normal patch management, with priority for systems handling untrusted captures.
Technical view
Wireshark 2.4.0 through 2.4.5 and 2.2.0 through 2.2.13 have a crash condition in the IEEE 802.15.4 dissector. The fix changed epan/dissectors/packet-ieee802154.c to ensure an allocation step occurs before use.
Likely exposure
Exposure is most likely on analyst workstations, troubleshooting hosts, and systems that open or capture IEEE 802.15.4 packet data using affected Wireshark versions.
Exploitation context
CISA KEV status is false in the supplied bundle. The cited material supports a crash condition, but does not document active exploitation, exploit availability, privilege impact, or code execution.
Researcher notes
The source bundle is limited: no CVSS vector, CWE, detailed trigger conditions, or exploitability assessment are provided. Analysis should stay scoped to a dissector crash and the named affected Wireshark version ranges.
Mitigation direction
- Inventory Wireshark installations and identify versions 2.4.0-2.4.5 and 2.2.0-2.2.13.
- Update Wireshark using upstream or distribution security guidance.
- Prioritize systems used to inspect untrusted capture files or wireless packet data.
- Review Debian LTS advisories if using Debian-packaged Wireshark.
- Check vendor release notes for the package containing the referenced upstream fix.
Validation and detection
- Confirm installed Wireshark versions are outside the affected ranges.
- Verify package changelogs include CVE-2018-9260 or the referenced upstream fix.
- Identify workflows that process IEEE 802.15.4 captures or live traffic.
- Confirm analysts do not rely on unsupported affected Wireshark branches.
- Document residual exposure where upgrades are delayed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-9260 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=14d6f717d8ea27688af48532edb1d29f502ea8f0CVE reference · x_refsource_MISC
- https://www.wireshark.org/security/wnpa-sec-2018-17.htmlCVE reference · x_refsource_MISC
- [debian-lts-announce] 20190115 [SECURITY] [DLA 1634-1] wireshark security updateCVE reference · mailing-list, x_refsource_MLIST
- [debian-lts-announce] 20180528 [SECURITY] [DLA 1388-1] wireshark security updateCVE reference · mailing-list, x_refsource_MLIST
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14468CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
