dbcve.org
WiresharkApplication

CVE-2018-14341

HIGH · 7.5 CVSS v3.0 Published 2018-07-19
Fix available
A fix is available. Upgrade to after 2.6.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a denial-of-service vulnerability in Wireshark's DICOM protocol dissector. A malformed DICOM packet can cause an offset overflow, leading to an infinite or large loop in the dissector code. The vulnerability is located in epan/dissectors/packet-dcm.c.

MitigationUpgrade Wireshark to version 2.6.2, 2.4.8, or 2.2.16 or later, which contain the offset overflow fix in the DICOM dissector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WiresharkApplication
Affected:>= 2.2.0, <= 2.2.15>= 2.4.0, <= 2.4.7>= 2.6.0, <= 2.6.1
Debian LinuxOperating system
Affected:= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Wireshark installation
    Run 'wireshark --version' or check your package manager for installed wireshark packages
    Affected if Wireshark is installed and the version falls within 2.2.0-2.2.15, 2.4.0-2.4.7, or 2.6.0-2.6.1
  2. Confirm DICOM dissector is loaded
    Open Wireshark and check if DICOM protocol support is available - go to Analyze > Enabled Protocols and verify 'DICOM' is enabled, or run 'tshark -G protocols' and grep for DICOM
    Affected if DICOM protocol dissector is enabled in Wireshark
  3. Identify DICOM traffic capture or review
    Review any packet capture files (.pcap, .pcapng) you are analyzing, or monitor live network traffic, for DICOM traffic which uses port 104 or 11112 by default
    Affected if You are actively analyzing or will analyze DICOM protocol traffic

You are affected if you have a vulnerable Wireshark version (2.2.0-2.2.15, 2.4.0-2.4.7, or 2.6.0-2.6.1) AND you process DICOM protocol traffic with the dissector enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.6.1
Interim mitigation

Upgrade Wireshark to version 2.6.2, 2.4.8, or 2.2.16 or later, which contain the offset overflow fix in the DICOM dissector.

Fix this in Wireshark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14341 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data