Security readout for executives and security teams
Plain-English summary
CVE-2018-9272 is a Wireshark memory leak in the H.223 packet dissector. It affects Wireshark 2.4.0 through 2.4.5 and 2.2.0 through 2.2.13. The public bundle does not provide CVSS, CWE, impact detail, or active exploitation evidence.
Executive priority
Prioritize as routine remediation unless Wireshark is used heavily on untrusted captures. The available evidence supports cleanup and inventory action, not emergency response.
Technical view
The issue is described as a memory leak in epan/dissectors/packet-h223.c in specified Wireshark 2.4.x and 2.2.x releases. Evidence points to parser-level resource leakage during H.223 dissection, but the provided sources do not state trigger conditions, crashability, or exploitability.
Likely exposure
Exposure is most likely on analyst workstations, servers, or workflows running the affected Wireshark versions and processing captures that reach the H.223 dissector.
Exploitation context
CISA KEV is false in the bundle, and no cited source here states active exploitation. Treat exploitation status as unconfirmed.
Researcher notes
The source bundle is thin: no CVSS, CWE, detailed impact, or proof of active exploitation. Keep analysis tied to version exposure and vendor advisory confirmation.
Mitigation direction
- Identify any Wireshark 2.4.0-2.4.5 or 2.2.0-2.2.13 installations.
- Consult Wireshark advisory WNPA-SEC-2018-24 for fixed release guidance.
- Upgrade affected Wireshark installations to a vendor-supported non-affected release.
- Limit processing of untrusted packet captures until affected installations are remediated.
Validation and detection
- Check installed Wireshark versions across analyst endpoints and build images.
- Confirm whether affected systems process packet captures from external or untrusted sources.
- Review Wireshark advisory WNPA-SEC-2018-24 and the linked commit for remediation evidence.
- After upgrade, verify systems no longer report affected 2.2.x or 2.4.x versions.
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-9272 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=6e3b90824a82724f445a0374e99f0b76e4cf5e8bCVE reference · x_refsource_MISC
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14487CVE reference · x_refsource_MISC
- https://www.wireshark.org/security/wnpa-sec-2018-24.htmlCVE 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.