WiresharkApplication
CVE-2018-11355
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.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
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 2.6.0 contains a buffer overflow vulnerability in the RTCP (Real-time Transport Control Protocol) dissector located in epan/dissectors/packet-rtcp.c. The vulnerability is triggered when processing malformed packet status chunks, leading to a crash. This is a denial-of-service vulnerability with high availability impact.
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.6.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' from command line, or check installed packages via system package managerAffected if Wireshark is not installed - not affected
-
Identify the exact Wireshark versionExamine the version output from the previous step - look for version number 2.6.0 specificallyAffected if Version displayed is exactly 2.6.0 - likely affected
-
Confirm RTCP dissector presenceVerify the dissector file packet-rtcp.c exists in the Wireshark installation directory under epan/dissectors/Affected if File exists in version 2.6.0 installation - vulnerability is present in this component
-
Determine if RTCP traffic is being processedInspect active capture files or live network interfaces that Wireshark or TShark is analyzing - look for RTCP packets in the captureAffected if RTCP packets from untrusted sources are being dissected in Wireshark 2.6.0 - exploitation condition met
User is affected if Wireshark version 2.6.0 is installed and the RTCP dissector is processing traffic from untrusted sources, as the buffer overflow in packet-rtcp.c triggers on malformed packet status chunks.
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.6.1 or later where the buffer overflow in packet-rtcp.c has been addressed. Alternatively, avoid opening capture files or processing network traffic from untrusted sources with vulnerable Wireshark versions.
Fix this in Wireshark
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11355 — 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-11355 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