WiresharkApplication
CVE-2018-7320
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 · uneditedIn Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the SIGCOMP protocol dissector could crash. This was addressed in epan/dissectors/packet-sigcomp.c by validating operand offsets.
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 confidenceThe SIGCOMP protocol dissector in Wireshark contains a crash vulnerability due to insufficient validation of operand offsets when parsing SIGCOMP messages. By sending a specially crafted packet with malformed operand offsets, an attacker can trigger a crash in Wireshark's dissector, causing a denial of service.
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
>= 2.2.0, <= 2.2.12>= 2.4.0, <= 2.4.4
Debian LinuxOperating system
= 8.0= 9.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Wireshark is installedRun 'wireshark --version' or 'tshark --version' on the system. If neither command returns version information, Wireshark is not installed.Affected if Wireshark is installed and the command returns version information.
-
Identify the installed Wireshark versionExecute 'wireshark --version 2>&1 | head -1' or 'tshark --version 2>&1 | head -1' and note the version number returned (for example, 2.4.0 or 2.2.12).Affected if The command returns a version number.
-
Compare against affected version range 2.2.xIf the installed version starts with 2.2., verify whether it falls within 2.2.0 through 2.2.12 inclusive. Check the minor version number after 2.2.Affected if The version is 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 2.2.9, 2.2.10, 2.2.11, or 2.2.12.
-
Compare against affected version range 2.4.xIf the installed version starts with 2.4., verify whether it falls within 2.4.0 through 2.4.4 inclusive. Check the minor version number after 2.4.Affected if The version is 2.4.0, 2.4.1, 2.4.2, 2.4.3, or 2.4.4.
-
Check for Debian-specific package versionOn Debian systems, run 'dpkg -l | grep wireshark' or 'apt-cache policy wireshark' to obtain the installed package version.Affected if The installed Debian package version corresponds to the affected Wireshark versions.
The environment is affected if Wireshark is installed and the version is 2.2.0-2.2.12 or 2.4.0-2.4.4, since these versions contain the vulnerable SIGCOMP dissector that can crash when processing malformed operand offsets.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Wireshark to version 2.4.5 or 2.2.13 or later to obtain the patched dissector that properly validates operand offsets before processing.
Fix this in Wireshark
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-7320 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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