WiresharkApplication
CVE-2015-8711
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 · uneditedepan/dissectors/packet-nbap.c in the NBAP dissector in Wireshark 1.12.x before 1.12.9 and 2.0.x before 2.0.1 does not validate conversation data, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted packet.
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 NBAP dissector in Wireshark (packet-nbap.c) fails to validate conversation data before use, allowing a crafted malicious packet to trigger a NULL pointer dereference and crash the application.
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
= 1.12.0= 1.12.1= 1.12.2= 1.12.3= 1.12.4= 1.12.5= 1.12.6= 1.12.7= 1.12.8= 2.0.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 check Help > About Wireshark to see the exact version numberAffected if Version is 1.12.0 through 1.12.8, or version 2.0.0 exactly (versions 1.12.9+ and 2.0.1+ are fixed)
-
Verify NBAP dissector is availableOpen Wireshark, go to Analyze > Enabled Protocols, search for NBAP in the list and confirm it is enabledAffected if NBAP protocol dissector is enabled in the protocol settings
-
Confirm NBAP traffic is being captured or loadedCapture network traffic or open a pcap file containing NBAP (Node B Application Part) protocol traffic, or filter using 'nbap' to see if such traffic existsAffected if NBAP protocol traffic is present in the capture or file being analyzed
-
Observe application stability during NBAP dissectionLoad a pcap file with NBAP traffic or capture NBAP traffic in real-time while Wireshark processes the packetsAffected if Wireshark crashes or becomes unresponsive when processing NBAP packets (NULL pointer dereference in packet-nbap.c)
You are affected if you are running Wireshark version 1.12.0-1.12.8 or 2.0.0 AND you are analyzing NBAP protocol traffic, as the unvalidated conversation data will trigger a NULL pointer dereference crash.
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 1.12.9 or later (for 1.12.x branches) or 2.0.1 or later (for 2.0.x branches).
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-2015-8711 — 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-2015-8711 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