WiresharkApplication
CVE-2010-2992
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 · uneditedpacket-gsm_a_rr.c in the GSM A RR dissector in Wireshark 1.2.2 through 1.2.9 allows remote attackers to cause a denial of service (crash) via unknown vectors that trigger a NULL pointer dereference.
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 confidenceWireshark 1.2.2 through 1.2.9 contains a NULL pointer dereference vulnerability in the GSM A RR dissector (packet-gsm_a_rr.c). Remote attackers can trigger this vulnerability by sending specially crafted network packets that cause the dissector to crash when parsing malformed GSM A interface RR messages.
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.2.2= 1.2.3= 1.2.4= 1.2.5= 1.2.6= 1.2.7= 1.2.8= 1.2.9CVSS 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.
-
Check if Wireshark is installedRun 'wireshark --version' or 'tshark --version' from command line, or check your application's About dialogAffected if Wireshark is present on the system
-
Identify the installed Wireshark versionExecute 'wireshark -v' or 'tshark -v' and note the version number displayedAffected if Version is 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.8, or 1.2.9
-
Verify the GSM A RR dissector is availableOpen Wireshark, go to Analyze > Enabled Protocols, then search for 'gsm_a_rr' or 'GSM A RR' in the protocol listAffected if The GSM A RR dissector is enabled in the protocol settings
-
Check for recent GSM A interface traffic capturesReview pcap files or live captures for packets using the GSM A interface protocol (filter by 'gsm_a.rr' or examine packet details for RR messages)Affected if You have captured or are actively processing GSM A RR traffic from untrusted sources
You are affected if Wireshark version 1.2.2 through 1.2.9 is installed AND the GSM A RR dissector is enabled AND you process GSM A traffic from potentially malicious capture files or network streams.
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 dataUpdate Wireshark to version 1.2.10 or later, which contains the patch for this vulnerability. As a defensive measure, consider disabling the GSM A RR dissector if not needed or using Wireshark's packet limiting features to reduce exposure to untrusted capture files.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2992 — 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-2992 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