Security readout for executives and security teams
Plain-English summary
This Wireshark issue can make the application crash or consume excessive memory while processing openSAFETY traffic. The main business impact is analyst workstation disruption and possible interruption of packet-analysis workflows, not confirmed system compromise.
Executive priority
Treat as a focused remediation item for packet-analysis environments. It is not presented as remote code execution or actively exploited, but it can disrupt security and engineering workflows using vulnerable Wireshark versions.
Technical view
Wireshark through 2.0.13 and 2.2.x through 2.2.7 had incomplete length validation in the openSAFETY dissector. The fix updated epan/dissectors/packet-opensafety.c. The CVE notes this resulted from an incomplete fix for CVE-2017-9350.
Likely exposure
Exposure is most likely on systems running affected Wireshark versions that inspect openSAFETY traffic or open packet captures containing openSAFETY data. The source bundle does not identify other affected products.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not marked KEV. The described impact is denial of service through crash or memory exhaustion during dissection.
Researcher notes
The public CVE description ties the bug to missing length validation in packet-opensafety.c and an incomplete CVE-2017-9350 fix. Available evidence supports denial of service only; no CVSS, CWE, exploit status, or broader product scope is provided.
Mitigation direction
- Upgrade Wireshark beyond the affected versions according to the Wireshark advisory.
- Prioritize analyst workstations that inspect industrial or openSAFETY-related traffic.
- Avoid opening untrusted packet captures on affected versions until upgraded.
- Review vendor guidance for any temporary operational workarounds.
Validation and detection
- Inventory installed Wireshark versions across analyst and engineering workstations.
- Flag Wireshark through 2.0.13 and 2.2.x through 2.2.7 as affected.
- Confirm upgraded builds include the openSAFETY length-validation fix.
- Check whether teams process openSAFETY traffic or untrusted capture files.
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-11411 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://www.wireshark.org/security/wnpa-sec-2017-28.htmlCVE reference · x_refsource_CONFIRM
- https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=a83a324acdfc07a0ca8b65e6ebaba3374ab19c76CVE reference · x_refsource_CONFIRM
- https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13755CVE reference · x_refsource_CONFIRM
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.