ChromeWeb browser · Google
CVE-2012-2895
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 · uneditedThe 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 vectors that trigger out-of-bounds write operations.
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 confidenceOut-of-bounds write vulnerability in Google Chrome's PDF rendering engine before version 22.0.1229.79. Attackers can craft malicious PDF files that cause memory corruption by writing beyond allocated buffer boundaries, potentially leading to denial of service or arbitrary 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
<= 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.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionOpen Google Chrome, click the menu icon (three dots) in the top right, select Help, then select About Google Chrome. Alternatively, navigate to chrome://version in the address bar.Affected if The version listed is 22.0.1229.78 or lower, or matches any of the specific affected versions 22.0.1229.0 through 22.0.1229.11
-
Verify PDF viewer is enabledNavigate to chrome://plugins in the address bar. Locate the 'Chrome PDF Viewer' plugin in the list and confirm its status.Affected if The Chrome PDF Viewer plugin is enabled or set to 'Always allowed to run'
-
Confirm PDFium component versionNavigate to chrome://components in the address bar. Look for the PDF component listed and note its version number if displayed.Affected if The PDF component version matches the Chrome version (22.0.1229.x range) and is prior to 22.0.1229.79
-
Review recently opened PDF filesCheck the Chrome download history (chrome://downloads) or the local system for any recently opened or downloaded PDF files that were not intentionally accessed by the user.Affected if Unknown or suspicious PDF files appear in the download history that the user did not intentionally open
A user is affected if they are running Google Chrome version 22.0.1229.78 or lower (or any version from 22.0.1229.0 to 22.0.1229.11) with the Chrome PDF Viewer enabled and have opened or could open a malicious PDF file.
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 Google Chrome to version 22.0.1229.79 or later to patch the vulnerability.
Fix this in Chrome
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-2012-2895 — 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-2895 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