WiresharkApplication
CVE-2010-2994
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 · uneditedStack-based buffer overflow in the ASN.1 BER dissector in Wireshark 0.10.13 through 1.0.14 and 1.2.0 through 1.2.9 has unknown impact and remote attack vectors. NOTE: this issue exists because of a CVE-2010-2284 regression.
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 confidenceStack-based buffer overflow in Wireshark's ASN.1 BER dissector allows remote attackers to crash the application or potentially execute arbitrary code via specially crafted network packets. This vulnerability is a regression of CVE-2010-2284 and affects versions 0.10.13 through 1.0.14 and 1.2.0 through 1.2.9.
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
= 0.10.13= 0.10.14= 1.0= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Wireshark installationRun 'wireshark --version' or check for Wireshark in installed programsAffected if Wireshark is installed on the system
-
Identify installed Wireshark versionExecute 'wireshark --version' and note the full version number (e.g., 1.0.14, 1.2.9)Affected if The version falls within 0.10.13 to 1.0.14 or 1.2.0 to 1.2.9
-
Check if ASN.1 BER dissector is activeOpen Wireshark, go to Analyze -> Enabled Protocols, and look for 'BER' or 'ASN.1' in the protocol list. The dissector is built-in and available by default.Affected if BER/ASN.1 dissector is enabled (this is the default state)
-
Determine if processing untrusted captures is occurringReview recent capture file sources or check if the system is frequently opening packet capture (.pcap) files from external or untrusted sourcesAffected if The system is opening packet captures from untrusted or unknown origins
A user is affected if Wireshark is installed with a version between 0.10.13-1.0.14 or 1.2.0-1.2.9 and the ASN.1 BER dissector is enabled while processing untrusted network packet captures.
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.
dbcve · scopedUpgrade to Wireshark version 1.0.15 or later, or version 1.2.10 or later. Alternatively, avoid opening packet captures from untrusted sources as the exploit is triggered during packet dissection.
Wireshark 1.0.15+ or 1.2.10+ (or current stable release)
- 1. Download Wireshark from the official website (https://www.wireshark.org/download.html) or your system's package manager
- 2. Uninstall the current vulnerable version of Wireshark
- 3. Install Wireshark version 1.0.15 or later (or version 1.2.10 or later for the 1.2.x branch)
- 4. Verify the installation by checking the version number in Wireshark (Help > About Wireshark)
Generated from the published advisory — verify against the referenced sources before acting.
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-2010-2994 — 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-2010-2994 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