Security readout for executives and security teams
Plain-English summary
This flaw can make vulnerable Wireshark versions hang while dissecting DICOM traffic. The likely business impact is disruption to packet analysis or monitoring workflows, not data theft or system takeover based on the supplied sources.
Executive priority
Treat as a targeted reliability risk for teams using Wireshark on medical or untrusted network data. Prioritize routine patching, with higher urgency for security operations or healthcare network analysis systems.
Technical view
Wireshark 2.2.0 through 2.2.6 and 2.0.0 through 2.0.12 contain an infinite loop in the DICOM dissector. The cited fix validates a length value in epan/dissectors/packet-dcm.c. No CVSS, CWE, or detailed impact score is provided.
Likely exposure
Exposure is most likely where Wireshark or tshark processes untrusted packet captures or live traffic containing DICOM protocol data, especially in healthcare or diagnostic network environments.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Public bug, fuzzing, advisory, and commit references indicate the issue was known and fixed publicly in 2017.
Researcher notes
Evidence supports an infinite-loop parser flaw fixed by length validation. The supplied data lacks CVSS, CWE, exploit details, and confirmed active exploitation, so avoid stronger claims without additional vendor or threat-intelligence evidence.
Mitigation direction
- Upgrade Wireshark beyond the affected 2.2.x and 2.0.x versions.
- Apply relevant vendor or distribution security updates, including Debian guidance where applicable.
- Avoid processing untrusted DICOM captures with affected versions until upgraded.
- Check Wireshark vendor advisory for supported fixed release details.
Validation and detection
- Inventory Wireshark and tshark versions on analyst workstations and monitoring hosts.
- Confirm no systems run Wireshark 2.2.0-2.2.6 or 2.0.0-2.0.12.
- Verify package changelogs or vendor advisories reference WNPA-SEC-2017-27 or CVE-2017-9349.
- Identify workflows that parse DICOM traffic or captures from untrusted sources.
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-9349 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=cb1b6494c44c9e939d9e2554de6b812de395e3f9CVE reference · x_refsource_MISC
- https://www.wireshark.org/security/wnpa-sec-2017-27.htmlCVE reference · x_refsource_MISC
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1329CVE reference · x_refsource_MISC
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13685CVE reference · x_refsource_MISC
- [debian-lts-announce] 20190325 [SECURITY] [DLA 1729-1] wireshark security updateCVE reference · mailing-list, x_refsource_MLIST
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.