dbcve.org
ChromeWeb browser · Google

CVE-2012-2833

HIGH · 7.5 CVSS v2.0 Published 2012-06-27
Fix available
A fix is available. Upgrade to after 20.0.1132.42 or later.
See remediation →
84/100
Remediation priority · High
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
Buffer overflow in the JS API in the PDF functionality in Google Chrome before 20.0.1132.43 allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.

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

Buffer overflow vulnerability in the JavaScript API of Chrome's built-in PDF viewer allows remote attackers to cause denial of service or potentially execute arbitrary code via unspecified vectors, affecting versions prior to 20.0.1132.43.

MitigationUpdate Google Chrome to version 20.0.1132.43 or later to remediate this vulnerability. Organizations should deploy the browser update through their standard patch management process.

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
Affected:<= 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.10

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/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 checks

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

  1. Check installed Chrome version
    Open Chrome, navigate to chrome://version, or run 'google-chrome --version' from command line
    Affected if version is 20.0.1132.42 or lower, or matches any version from 20.0.1132.0 through 20.0.1132.10
  2. Verify PDF viewer is enabled
    Navigate to chrome://plugins in Chrome and locate the 'Chrome PDF Viewer' entry, or check chrome://settings for PDF handling settings
    Affected if Chrome PDF Viewer plugin is present and enabled (this is the default state)
  3. Confirm PDF functionality is accessible
    Attempt to open a PDF file in Chrome or visit a page with an embedded PDF to confirm the viewer is active
    Affected if PDF files load or render in the browser, indicating the vulnerable component is active

User is affected if Chrome version is 20.0.1132.42 or lower (including all 20.0.1132.0 through 20.0.1132.10 versions) and the built-in PDF viewer is enabled and functional.

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
Upgrade available Upgrade to a release after 20.0.1132.42
Interim mitigation

Update Google Chrome to version 20.0.1132.43 or later to remediate this vulnerability. Organizations should deploy the browser update through their standard patch management process.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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