WiresharkApplication
CVE-2018-7323
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-wccp.c had a large loop that was addressed by ensuring that a calculated length was monotonically increasing.
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 · moderate confidenceWireshark's WCCP (Web Cache Communication Protocol) dissector (packet-wccp.c) contained a vulnerability where a large loop could occur due to improper length validation. The fix ensures that a calculated length is monotonically increasing, preventing potential infinite loops or buffer-related issues when processing malformed WCCP packets.
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
= 7.0= 8.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' to get the Wireshark version. On Debian systems, also check with 'dpkg -l wireshark' or 'apt show wireshark'.Affected if Wireshark is installed and the version falls within 2.2.0-2.2.12 or 2.4.0-2.4.4
-
Identify the exact Wireshark versionExamine the version output - look for the full version number (e.g., 2.2.10, 2.4.3). Compare this against the affected ranges: 2.2.0 through 2.2.12, and 2.4.0 through 2.4.4.Affected if The installed version is any release from 2.2.0 to 2.2.12 inclusive, or 2.4.0 to 2.4.4 inclusive
-
Determine if WCCP traffic will be parsedWCCP (Web Cache Communication Protocol) dissector is built into Wireshark and loads automatically when processing packet captures containing WCCP packets (typically uses UDP ports 2048 and 70xx). If you open pcap files or capture from networks using WCCP, this dissector will be invoked.Affected if You open pcap files or capture from networks that contain WCCP protocol traffic while using a vulnerable Wireshark version
You are affected if Wireshark version is between 2.2.0-2.2.12 or 2.4.0-2.4.4 AND you open pcap files or capture from environments that contain WCCP traffic.
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 dataUpgrade Wireshark to version 2.4.5 or 2.2.13 or later. Alternatively, avoid opening untrusted packet capture files or limit Wireshark's use to trusted network environments until the upgrade can be applied.
Fix this in Wireshark
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7323 — 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-7323 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