dbcve.org
WiresharkApplication

CVE-2018-7418

HIGH · 7.5 CVSS v3.0 Published 2018-02-23
Fix available
A fix is available. Upgrade to after 2.4.4 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.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the SIGCOMP dissector could crash. This was addressed in epan/dissectors/packet-sigcomp.c by correcting the extraction of the length value.

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

The SIGCOMP dissector in Wireshark 2.2.0-2.2.12 and 2.4.0-2.4.4 contains a flaw in epan/dissectors/packet-sigcomp.c where the length value is incorrectly extracted, causing a crash when processing malformed SIGCOMP packets. This is a denial-of-service vulnerability exploitable via specially crafted packet captures.

MitigationUpgrade Wireshark to version 2.2.13 or later (2.2.x) or 2.4.5 or later (2.4.x). Avoid opening untrusted packet capture files until the update is applied.

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.12>= 2.4.0, <= 2.4.4
Debian LinuxOperating system
Affected:= 7.0= 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. Check installed Wireshark version
    Run 'wireshark --version' or 'tshark --version' from command line to identify the exact version number
    Affected if The version falls within 2.2.0 through 2.2.12 or 2.4.0 through 2.4.4
  2. Confirm Wireshark edition and build
    Check if the installation is a standard Wireshark build (not a modified distribution version) by running 'wireshark -v' or reviewing the package details
    Affected if The build includes the SIGCOMP dissector module from the affected versions
  3. Verify SIGCOMP dissector presence
    Open Wireshark GUI, go to Help > About Wireshark > Plugins or run 'wireshark -G plugins' to list compiled dissectors
    Affected if The packet-sigcomp dissector is loaded and available for processing captures

You are affected if Wireshark version 2.2.0-2.2.12 or 2.4.0-2.4.4 is installed and the SIGCOMP dissector is present, as the incorrect length extraction vulnerability in packet-sigcomp.c will trigger on malformed SIGCOMP packets.

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.4.4
Interim mitigation

Upgrade Wireshark to version 2.2.13 or later (2.2.x) or 2.4.5 or later (2.4.x). Avoid opening untrusted packet capture files until the update is applied.

Fix this in Wireshark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7418 — 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-7418 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