ChromeWeb browser · Google
CVE-2012-2888
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 · uneditedUse-after-free vulnerability 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 involving SVG text references.
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 confidenceUse-after-free vulnerability in Google Chrome's SVG text reference handling allows remote attackers to access freed memory, potentially causing denial of service or arbitrary code execution. The flaw exists in versions before 22.0.1229.79 and is triggered through specially crafted SVG content.
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.11= 12.1= 12.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionOpen Chrome, click the menu icon (three dots), select Help, then About Google Chrome. Alternatively, navigate to chrome://settings/help in the address bar.Affected if The displayed version is 22.0.1229.78 or lower, or matches any of these specific versions: 22.0.1229.0 through 22.0.1229.11 (excluding 22.0.1229.79 and later)
-
Check Chrome version via command lineOn Windows, open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. On Linux, run: google-chrome --version or chrome --version.Affected if The reported version matches the vulnerable range listed above (22.0.1229.78 or lower, or any version from 22.0.1229.0 to 22.0.1229.11)
-
Check for Chrome packages on OpenSUSEOpen a terminal and run: rpm -qa | grep -i chrome or zypper se google-chromeAffected if The installed Chrome package version corresponds to a vulnerable release (OpenSUSE 12.1 and 12.2 shipped with vulnerable Chrome versions)
-
Review browsing exposure to SVG contentNote that the vulnerability is triggered when processing specially crafted SVG text reference elements. Users who browse untrusted websites or open SVG files are potentially exposed.Affected if Users process SVG content from untrusted sources in a vulnerable Chrome version
You are affected if Google Chrome version 22.0.1229.78 or lower, or any version from 22.0.1229.0 to 22.0.1229.11, is installed and the browser processes SVG content.
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. For organizations, deploy the updated browser version enterprise-wide and verify remediation in controlled testing environments before production rollout.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2888 — 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-2888 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