ChromeWeb browser · Google
CVE-2012-2834
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 · uneditedInteger overflow in Google Chrome before 20.0.1132.43 allows remote attackers to cause a denial of service or possibly have unspecified other impact via crafted data in the Matroska container format.
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 confidenceInteger overflow vulnerability in Google Chrome's Matroska container demuxer (used for parsing .mkv video files) allows remote attackers to trigger the overflow via specially crafted Matroska files, potentially leading to denial of service or unspecified code execution.
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
ChromeWeb browser
<= 20.0.1132.42= 20.0.1132.0= 20.0.1132.1= 20.0.1132.2= 20.0.1132.3= 20.0.1132.4= 20.0.1132.5= 20.0.1132.6= 20.0.1132.7= 20.0.1132.8= 20.0.1132.9= 20.0.1132.10CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Check installed Chrome versionNavigate to chrome://version in the browser address bar, or run 'google-chrome --version' from the command lineAffected if Version is 20.0.1132.0 through 20.0.1132.42, or any version number equal to or below 20.0.1132.42
-
Verify Chrome can handle Matroska filesAttempt to open any .mkv file in Chrome, or check if Chrome is set as the default handler for MKV files in the OSAffected if Chrome successfully plays or attempts to parse MKV files, confirming the Matroska demuxer is active
-
Identify exposure to untrusted MKV contentReview browser usage: check download folder for MKV files, check extensions/plugins that auto-load MKV content from web pages, or check if Chrome is used as embedded player for web videoAffected if Chrome processes MKV files from sources that are not fully trusted (downloads, web content, email attachments)
User is affected if Chrome version falls between 20.0.1132.0 and 20.0.1132.42 inclusive and the browser handles Matroska (.mkv) files from any source, since the vulnerable demuxer is built into these versions.
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 · scopedUpdate Google Chrome to version 20.0.1132.43 or later to patch the vulnerability; users should avoid opening untrusted Matroska files until the update is applied.
Chrome 20.0.1132.43 or later
- Open Google Chrome
- Navigate to chrome://settings/help or click Help > About Google Chrome
- Allow Chrome to check for updates
- If version 20.0.1132.43 or later is available, click 'Update Google Chrome'
- Restart Chrome to apply the update
- Alternatively, download and install the latest Chrome version from https://www.google.com/chrome/
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 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-2012-2834 — 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-2012-2834 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