WiresharkApplication
CVE-2018-7337
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, the DOCSIS protocol dissector could crash. This was addressed in plugins/docsis/packet-docsis.c by removing the recursive algorithm that had been used for concatenated PDUs.
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 confidenceA crash vulnerability exists in Wireshark 2.4.0 through 2.4.4's DOCSIS protocol dissector caused by a recursive algorithm used to handle concatenated PDUs (Protocol Data Units). When parsing specially crafted DOCSIS capture files, the recursive logic leads to a stack overflow or memory corruption resulting in application termination.
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.4.0, <= 2.4.4
Debian LinuxOperating system
= 7.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.
-
Determine installed Wireshark versionRun 'wireshark --version' or 'tshark --version' from command line to get the exact version numberAffected if Version is 2.4.0, 2.4.1, 2.4.2, 2.4.3, or 2.4.4
-
Verify DOCSIS protocol dissector is presentCheck that Wireshark includes DOCSIS protocol support - look for 'docsis' in the list of enabled protocols under Analyze > Enabled Protocols in the GUI, or check 'tshark -G protocols' output for docsisAffected if DOCSIS protocol dissector is enabled and available for use
-
Identify if DOCSIS capture files may be processedReview any packet capture files with .pcap, .pcapng, or similar extensions that may contain DOCSIS traffic; check if Wireshark is used to analyze network captures from cable modem or DOCSIS-based networksAffected if User opens or processes DOCSIS capture files with the affected Wireshark version
User is affected if Wireshark version is between 2.4.0 and 2.4.4 inclusive and the DOCSIS dissector is used to open capture files.
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 later where the recursive algorithm has been removed from the DOCSIS dissector. Alternatively, avoid opening untrusted DOCSIS capture files with vulnerable Wireshark versions.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7337 — 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-7337 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