dbcve.org
WiresharkApplication

CVE-2010-2995

HIGH · 10.0 CVSS v2.0 Published 2010-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The SigComp Universal Decompressor Virtual Machine (UDVM) in Wireshark 0.10.8 through 1.0.14 and 1.2.0 through 1.2.9 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via vectors related to sigcomp-udvm.c and an off-by-one error, which triggers a buffer overflow, different vulnerabilities than CVE-2010-2287.

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

Wireshark contains an off-by-one error in the SigComp Universal Decompressor Virtual Machine (UDVM) implementation in sigcomp-udvm.c. This triggers a buffer overflow that can be exploited via specially crafted SigComp packets, leading to denial of service (crash) and potentially arbitrary code execution.

MitigationUpgrade Wireshark to version 1.0.15 or later for the 1.0.x branch, or 1.2.10 or later for the 1.2.x branch. Alternatively, disable the SigComp dissector or block SigComp traffic at network perimeter devices.

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:= 0.10.8= 0.10.9= 0.10.10= 0.10.11= 0.10.12= 0.10.13= 0.10.14= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 installed Wireshark version
    Run 'wireshark -v' or 'tshark -v' from command line, or on Windows open Help > About Wireshark to see the exact version number
    Affected if Version is 0.10.8, 0.10.9, 0.10.10, 0.10.11, 0.10.12, 0.10.13, 0.10.14, 1.0.0, 1.0.1, 1.0.2, 1.0.3, or 1.0.4
  2. Verify if SigComp dissector is enabled
    In Wireshark UI go to Analyze > Enabled Protocols and look for 'sigcomp' in the list; or run 'tshark -G protocols' and grep for sigcomp to see if it is loaded
    Affected if The 'sigcomp' protocol is listed as enabled (not disabled)
  3. Confirm SigComp traffic is being processed
    Open a captured packet trace (pcap file) in Wireshark and apply filter 'sigcomp' or examine if any UDP/TCP packets use port 5000 (common SigComp port) or have SigComp content
    Affected if SigComp packets are visible in capture files or live traffic is being dissected with SigComp

You are affected if you have Wireshark version 0.10.8 through 1.0.4 running with the SigComp dissector enabled and processing SigComp traffic.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wireshark to version 1.0.15 or later for the 1.0.x branch, or 1.2.10 or later for the 1.2.x branch. Alternatively, disable the SigComp dissector or block SigComp traffic at network perimeter devices.

Recommended fix High confidence

Wireshark 1.0.15 (or later stable release such as 1.2.x/1.4.x/2.x/3.x/4.x)

  1. 1. Backup your current Wireshark configuration (typically located at ~/.wireshark/ or equivalent)
  2. 2. Uninstall the current version of Wireshark (0.10.8, 0.10.9, 0.10.10, or 0.10.11)
  3. 3. Download Wireshark 1.0.15 or later from the official Wireshark website (https://www.wireshark.org/download.html)
  4. 4. Install the new version following standard installation procedures
  5. 5. Verify the installation by checking Help > About Wireshark shows version 1.0.15 or higher
  6. 6. Test that packet capture functionality works correctly with your typical capture setup
Caveat Minimal risk - interface may have minor changes between 0.10.x and 1.0.x, configuration files are generally backward compatible

Generated from the published advisory — verify against the referenced sources before acting.

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-2010-2995 — 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-2010-2995 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