WiresharkApplication
CVE-2015-2189
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 · uneditedOff-by-one error in the pcapng_read function in wiretap/pcapng.c in the pcapng file parser in Wireshark 1.10.x before 1.10.13 and 1.12.x before 1.12.4 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via an invalid Interface Statistics Block (ISB) interface ID in 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 confidenceOff-by-one error in the pcapng file parser (pcapng_read function in wiretap/pcapng.c) allows out-of-bounds read when processing a crafted pcapng file with an invalid Interface Statistics Block (ISB) interface ID, causing Wireshark to crash.
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.10.0= 1.10.1= 1.10.2= 1.10.3= 1.10.4= 1.10.5= 1.10.6= 1.10.7= 1.10.8= 1.10.9= 1.10.10= 1.10.11
LinuxOperating system
= 7
Debian LinuxOperating system
= 7.0= 8.0= 11.2= 13.1= 13.2= 4.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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Confirm Wireshark installationRun `which wireshark` on Linux/Unix or check Programs and Features on Windows. Alternatively, use package queries: `rpm -q wireshark` (RHEL/OEL), `dpkg -l wireshark` (Debian), or `zypper se wireshark` (openSUSE).Affected if Wireshark is not installed on the system
-
Determine installed Wireshark versionExecute `wireshark --version` or check the package version via the package manager (e.g., `rpm -q wireshark`, `dpkg -s wireshark`, `zypper se wireshark`).Affected if The command fails or returns no version information
-
Compare version against affected rangeCompare your installed version to the affected Wireshark versions: 1.10.0 through 1.10.11. Note that versions 1.10.13, 1.12.4, and later are fixed.Affected if The installed version is 1.10.x where x is between 0 and 11 inclusive
-
Check distribution-specific packagesFor affected OS listed (Oracle Linux 7, Debian 7.0/8.0, openSUSE 13.1/13.2, Mageia 4.0, Oracle Solaris 11.2), verify the Wireshark package version provided by the distribution repository.Affected if The distribution-packaged Wireshark version matches the vulnerable 1.10.x range
You are affected if Wireshark is installed and its version falls within the 1.10.0 through 1.10.11 range, or if your distribution shipped a vulnerable package version for the listed OS versions.
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.10.13, 1.12.4, or later. Avoid opening untrusted pcapng files in Wireshark until patched.
Fix this in Wireshark
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2189 — 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-2189 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