dbcve.org
ChromeWeb browser · Google

CVE-2012-2820

MEDIUM · 5.0 CVSS v2.0 Published 2012-06-27
Fix available
A fix is available. Upgrade to after 20.0.1132.42 or later.
See remediation →
59/100
Remediation priority · Elevated
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
Google Chrome before 20.0.1132.43 does not properly implement SVG filters, which allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified 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 · high confidence

Google Chrome before version 20.0.1132.43 contains an improper implementation of SVG filters that allows an out-of-bounds read vulnerability. Remote attackers can exploit this to cause a denial of service via unspecified vectors involving malicious SVG filter content.

MitigationUpdate Google Chrome to version 20.0.1132.43 or later, or enable automatic updates to ensure the browser receives security patches.

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

AV:N/AC:L/Au:N/C:N/I:N/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
    On Windows: Check for chrome.exe in Program Files or the user profile. On macOS: Check /Applications/Google Chrome.app. On Linux: Check /usr/bin/google-chrome or /opt/google/chrome/google-chrome
    Affected if Google Chrome browser is present on the system
  2. Determine the installed Chrome version
    Open Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number will be displayed on that page.
    Affected if The version shown is 20.0.1132.42 or lower, or shows a version in the 20.0.1132.x series
  3. Compare version against affected range
    The affected versions are 20.0.1132.0 through 20.0.1132.42 (all subversions). If your installed version is 20.0.1132.43 or higher, you are not affected. If it is 20.0.1132.42 or lower, you are in the affected range.
    Affected if Installed version is 20.0.1132.42 or any version from 20.0.1132.0 through 20.0.1132.42

A user is affected if Google Chrome version 20.0.1132.42 or any version from 20.0.1132.0 through 20.0.1132.42 is installed and the browser is used to render untrusted SVG content.

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, or enable automatic updates to ensure the browser receives security patches.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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