WiresharkApplication
CVE-2016-9374
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.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable.
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 contains a buffer over-read vulnerability in the AllJoyn dissector (packet-alljoyn.c). The vulnerability stems from a length variable not properly tracking the state of a signature variable during packet parsing, causing the dissector to read beyond buffer boundaries when processing malicious network traffic or specially crafted capture files.
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.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.2.0= 2.2.1
Debian LinuxOperating system
= 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/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' to determine the installed versionAffected if The version is 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.2.0, or 2.2.1 (these are the affected versions)
-
Check if AllJoyn dissector is loadedExamine the Wireshark installation for the presence of packet-alljoyn.c or the compiled AllJoyn dissector moduleAffected if The AllJoyn dissector is present in the installation and can process capture files
-
Verify AllJoyn protocol support statusOpen Wireshark, go to Analyze > Enabled Protocols, and search for 'AllJoyn' to see if it is enabledAffected if AllJoyn protocol is enabled in the protocol settings
-
Review recently opened capture filesCheck Wireshark recent files list or manually review any pcap/pcapng files that may contain AllJoyn trafficAffected if You have opened capture files that could contain AllJoyn protocol traffic since installing the affected version
You are affected if Wireshark version 2.0.0 through 2.2.1 is installed AND the AllJoyn dissector is enabled and has been used to process 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.2.2/2.0.8 or later. Until patched, avoid opening untrusted capture files and consider disabling the AllJoyn dissector if not required.
Fix this in Wireshark
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9374 — 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-2016-9374 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