dbcve.org
ChromeWeb browser · Google

CVE-2012-2890

MEDIUM · 6.8 CVSS v2.0 Published 2012-09-26
Fix available
A fix is available. Upgrade to after 22.0.1229.78 or later.
See remediation →
77/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
Use-after-free vulnerability in the PDF functionality in Google Chrome before 22.0.1229.79 allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted document.

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

Use-after-free vulnerability in Google Chrome's PDF parsing functionality. When processing a specially crafted PDF document, the browser frees memory but a pointer to that memory is still accessed, leading to memory corruption. This can cause a crash (denial of service) or potentially allow arbitrary code execution.

MitigationUpdate Google Chrome to version 22.0.1229.79 or later. As a temporary workaround, consider disabling the built-in PDF viewer or avoiding opening untrusted PDF documents.

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:<= 22.0.1229.78= 22.0.1229.0= 22.0.1229.1= 22.0.1229.2= 22.0.1229.3= 22.0.1229.4= 22.0.1229.6= 22.0.1229.7= 22.0.1229.8= 22.0.1229.9= 22.0.1229.10= 22.0.1229.11

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 if Google Chrome is installed
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' in terminal
    Affected if Google Chrome is not installed or no version is returned
  2. Verify the installed Chrome version
    Note the full version number displayed (e.g., 22.0.1229.78)
    Affected if Version is 22.0.1229.0 through 22.0.1229.78, or matches any of the specific affected versions (22.0.1229.0 through 22.0.1229.11)
  3. Confirm PDF viewer is enabled
    Navigate to chrome://plugins in Chrome and look for 'Chrome PDF Viewer' plugin, or check if PDF files open inline in the browser
    Affected if Chrome PDF Viewer is enabled and the browser version falls within the affected range

You are affected if Google Chrome version 22.0.1229.0 through 22.0.1229.78 is installed and the built-in PDF viewer is enabled.

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 22.0.1229.78
Interim mitigation

Update Google Chrome to version 22.0.1229.79 or later. As a temporary workaround, consider disabling the built-in PDF viewer or avoiding opening untrusted PDF documents.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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