Security readout for executives and security teams
Plain-English summary
This flaw affects older Wireshark versions when they parse openSAFETY traffic. A specially crafted packet capture or traffic sample could make Wireshark crash or consume excessive memory, disrupting analysis workstations and investigations. The provided sources do not indicate code execution or confirmed active exploitation.
Executive priority
Treat this as a targeted operational resilience issue, not a broad enterprise compromise signal. Prioritize patching systems that process untrusted captures or industrial network traffic.
Technical view
Wireshark 2.2.0-2.2.6 and 2.0.0-2.0.12 had an openSAFETY dissector issue in packet-opensafety.c. The stated fix checks for a negative length, preventing crash or memory exhaustion during packet dissection. No CVSS, CWE, or KEV exploitation signal is provided.
Likely exposure
Exposure is most likely where analysts, SOC tools, or automated capture-processing systems use affected Wireshark versions to inspect openSAFETY traffic or untrusted packet captures.
Exploitation context
The source bundle describes denial-of-service behavior: crash or system memory exhaustion during parsing. KEV is false, and no cited source in the bundle confirms active exploitation in the wild.
Researcher notes
The public bundle is clear on affected Wireshark ranges and denial-of-service impact, but sparse on severity scoring, exploit maturity, and environmental prerequisites. Avoid assuming more than parser crash or memory exhaustion.
Mitigation direction
- Identify and retire Wireshark 2.2.0-2.2.6 and 2.0.0-2.0.12 installations.
- Apply Wireshark vendor updates containing the openSAFETY negative-length check.
- Avoid opening untrusted packet captures on affected analyst workstations.
- Check Wireshark guidance before relying on compensating controls.
Validation and detection
- Inventory Wireshark versions on analyst endpoints and capture-processing systems.
- Confirm affected versions are no longer present after patching.
- For source builds, verify the openSAFETY dissector includes the negative-length guard.
- Review crash and memory exhaustion reports from packet analysis systems.
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-2017-9350 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://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13649CVE reference · x_refsource_MISC
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=dbc7cb0bbdd501fa96e0cb98668f6d6bf17ac4e6CVE reference · x_refsource_MISC
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1212CVE reference · x_refsource_MISC
- https://www.wireshark.org/security/wnpa-sec-2017-28.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.