dbcve.org
WiresharkApplication

CVE-2016-4419

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

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-spice.c in the SPICE dissector in Wireshark 2.x before 2.0.2 mishandles capability data, which allows remote attackers to cause a denial of service (large loop) 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 · moderate confidence

The SPICE protocol dissector in Wireshark 2.x before 2.0.2 contains a vulnerability where capability data is mishandled, leading to a denial of service condition via a large loop when processing a crafted packet. This affects the dissector's ability to properly parse malformed capability negotiation data.

MitigationUpgrade Wireshark to version 2.0.2 or later to patch the vulnerable SPICE dissector code that improperly handles capability data.

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:= 2.0.0= 2.0.1

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

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

  1. Check Wireshark version
    Run 'wireshark --version' or open Wireshark and go to Help > About Wireshark to view the version number
    Affected if The installed version is 2.0.0 or 2.0.1
  2. Verify SPICE dissector is available
    Open Wireshark, go to Analyze > Enabled Protocols, and search for 'SPICE' in the protocol list
    Affected if The SPICE protocol dissector is present and enabled in the protocol list
  3. Confirm SPICE traffic capture or import
    Check if any recently opened capture files (.pcap, .pcapng) contain SPICE protocol packets, or if a live capture was actively capturing SPICE traffic
    Affected if SPICE protocol packets were being dissected or the capture file contains SPICE traffic that would trigger the vulnerable code path

You are affected if Wireshark version is 2.0.0 or 2.0.1 AND the SPICE dissector is enabled AND you are processing or have processed SPICE protocol traffic with crafted malformed capability negotiation data.

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 2.0.2 or later to patch the vulnerable SPICE dissector code that improperly handles capability data.

Fix this in Wireshark Scoped from the published advisory
  • Consultation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4419 — 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-2016-4419 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