WiresharkApplication
CVE-2018-7321
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, epan/dissectors/packet-thrift.c had a large loop that was addressed by not proceeding with dissection after encountering an unexpected type.
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 confidenceWireshark's Thrift dissector (packet-thrift.c) contained a large loop that would continue processing even after encountering an unexpected type during packet dissection. This could lead to excessive resource consumption or other issues when parsing maliciously crafted Thrift traffic.
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.4CVSS 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 installed Wireshark versionRun `wireshark --version` or `tshark --version` from command line to identify the exact version of Wireshark installed.Affected if The version falls within 2.2.0 to 2.2.12 inclusive, or 2.4.0 to 2.4.4 inclusive.
-
Identify if Thrift protocol dissector is availableOpen Wireshark, go to Analyze > Enabled Protocols, or run `tshark -G protocols | grep -i thrift` to confirm the Thrift dissector exists in this installation.Affected if Thrift protocol dissector is present and enabled by default in the affected versions.
-
Determine exposure to Thrift capture filesReview any recent packet capture files (.pcap, .pcapng) opened in Wireshark for Thrift-based traffic, or check if the system is capturing live network traffic that may contain Thrift protocol data.Affected if You have opened or are likely to open capture files containing Thrift protocol traffic.
-
Check for crash or hang events related to Thrift parsingReview Wireshark's crash logs or system event logs for any crashes or hangs that occurred while dissecting Thrift traffic, or test by opening a sample Thrift capture file if available.Affected if Wireshark exhibits excessive resource consumption, hangs, or crashes when processing Thrift-encapsulated traffic in the affected versions.
A user is affected if they have Wireshark versions 2.2.0-2.2.12 or 2.4.0-2.4.4 installed AND are likely to process Thrift protocol traffic through the dissector.
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, 2.2.13, or later. Avoid opening untrusted Thrift capture files.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7321 — 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-7321 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