LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9259: In Wireshark 2.4.0 to 2.4.5 and 2.2.0 to 2.2.13, the MP4 dissector could crash.

In Wireshark 2.4.0 to 2.4.5 and 2.2.0 to 2.2.13, the MP4 dissector could crash. This was addressed in epan/dissectors/file-mp4.c by restricting the box recursion depth.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2018-9259 is a Wireshark crash issue in the MP4 dissector. Affected Wireshark versions can fail when processing certain MP4 structures. Business impact is mainly analyst workstation disruption, not confirmed data theft or remote compromise.

Executive priority

Treat this as a low-priority hygiene update unless affected Wireshark is used heavily in security operations. It can interrupt investigations but the provided evidence does not indicate compromise, privilege escalation, or active exploitation.

Technical view

Wireshark 2.4.0 through 2.4.5 and 2.2.0 through 2.2.13 are affected. The MP4 dissector could crash because MP4 box recursion depth was not sufficiently restricted. The fix changed epan/dissectors/file-mp4.c to limit recursion depth.

Likely exposure

Exposure is most likely on analyst, engineering, or forensic systems running the affected Wireshark versions and opening MP4-related inputs. Server exposure is not indicated by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The credible impact is denial of service against Wireshark during file or traffic analysis.

Researcher notes

Focus validation on product version and parser exposure, not exploit reproduction. The key technical detail is an MP4 box recursion-depth restriction in file-mp4.c. The public records do not provide CVSS, CWE, or confirmed exploitation details.

Mitigation direction

  • Upgrade Wireshark using vendor guidance or supported OS security packages.
  • Remove Wireshark 2.4.0-2.4.5 and 2.2.0-2.2.13 from managed systems.
  • Limit use of affected Wireshark builds with untrusted MP4-related inputs.
  • Apply Debian LTS security updates where Debian packages are used.

Validation and detection

  • Inventory installed Wireshark versions on analyst and engineering workstations.
  • Confirm affected versions are no longer present after patching.
  • Review package-manager history for the referenced Debian security update where applicable.
  • Check vulnerability scanner results against CVE-2018-9259 after remediation.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-9259 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.