Security readout for executives and security teams
Plain-English summary
CVE-2017-9347 is a denial-of-service flaw in Wireshark 2.2.0 through 2.2.6. A malformed ROS protocol item could make Wireshark crash while analyzing traffic or a capture file. The business impact is analyst/tool disruption, not documented data theft or system takeover.
Executive priority
Treat this as a bounded operational resilience issue. It can interrupt packet analysis workflows, but the provided evidence does not show remote code execution, data compromise, or active exploitation.
Technical view
The Wireshark ROS dissector could dereference a NULL pointer when processing an invalid OID. The source bundle says the issue was fixed in epan/dissectors/asn1/ros/packet-ros-template.c by validating the OID. No CVSS, CWE, or CPE detail is provided.
Likely exposure
Exposure is most likely on analyst workstations, security appliances, or lab systems running Wireshark 2.2.0 to 2.2.6 and opening untrusted captures or dissecting ROS-related traffic.
Exploitation context
The bundle includes an Exploit-DB reference, so public exploit material exists. KEV is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Focus review on ROS dissector OID handling and crash reproduction boundaries. The available CVE data is sparse: no CVSS vector, CWE, or normalized affected CPEs are supplied.
Mitigation direction
- Upgrade affected Wireshark 2.2.0-2.2.6 installations using Wireshark vendor guidance.
- Avoid opening untrusted capture files on vulnerable Wireshark versions.
- Restrict vulnerable analysis systems from processing unsolicited or unknown traffic captures.
- Prioritize replacement of unsupported Wireshark builds on analyst workstations.
Validation and detection
- Inventory Wireshark versions and flag 2.2.0 through 2.2.6.
- Confirm the installed build includes the ROS OID validation fix.
- Review crash reports for Wireshark ROS dissector failures.
- Check whether teams process untrusted packet captures with affected 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-2017-9347 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.chromium.org/p/oss-fuzz/issues/detail?id=1216CVE reference · x_refsource_MISC
- https://www.wireshark.org/security/wnpa-sec-2017-31.htmlCVE reference · x_refsource_MISC
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13637CVE reference · x_refsource_MISC
- 42124CVE reference · exploit, x_refsource_EXPLOIT-DB
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=278e52f26e7e1a23f8d2e8ed98693328c992bdceCVE 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.