dbcve.org
WiresharkApplication

CVE-2015-3182

MEDIUM · 5.5 CVSS v3.0 Published 2016-01-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
epan/dissectors/packet-dec-dnart.c in the DECnet NSP/RT dissector in Wireshark 1.10.12 through 1.10.14 mishandles a certain strdup return value, which allows remote attackers to cause a denial of service (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 confidence

The DECnet NSP/RT dissector in Wireshark (packet-dec-dnart.c) fails to properly check the return value from the strdup() function. When strdup() fails due to memory allocation failure and returns NULL, the dissector proceeds to use this NULL pointer, leading to a NULL pointer dereference and application crash when processing a specially crafted packet.

MitigationUpgrade Wireshark to version 1.10.15 or later (or 1.12.x series) which contains the fix. Until then, avoid opening untrusted packet capture files or disable the DECnet NSP/RT dissector if not required.

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
Affected:= 1.10.12= 1.10.13= 1.10.14

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Wireshark version
    Run 'wireshark --version' or 'tshark --version' to get the installed version number
    Affected if Version is 1.10.12, 1.10.13, or 1.10.14
  2. Verify DECnet dissector is available
    Check if packet-dec-dnart.c is compiled into the Wireshark installation by examining the dissector directory or running 'wireshark -G dissectors' and searching for 'dec-dnart' or 'DECnet NSP'
    Affected if The DECnet NSP/RT dissector is present in the installation
  3. Confirm dissector can be triggered
    Look for any existing pcap files that may contain DECnet traffic, or check if Wireshark has processed captures where DECnet protocols were dissected
    Affected if DECnet traffic has been parsed by the vulnerable dissector in any capture file

A user is affected if they have Wireshark version 1.10.12, 1.10.14, or 1.10.14 installed AND the DECnet NSP/RT dissector is enabled and has processed or could process a specially crafted packet.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wireshark to version 1.10.15 or later (or 1.12.x series) which contains the fix. Until then, avoid opening untrusted packet capture files or disable the DECnet NSP/RT dissector if not required.

Fix this in Wireshark Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-3182 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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