ChromeWeb browser · Google
CVE-2012-5147
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 24.0.1312.52 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to DOM handling.
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 confidenceA use-after-free vulnerability exists in Google Chrome versions prior to 24.0.1312.52. The flaw occurs during DOM handling operations, where memory is accessed after it has been freed, potentially allowing remote attackers to cause a denial of service or achieve unspecified 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
<= 24.0.1312.51= 24.0.1272.0= 24.0.1272.1= 24.0.1273.0= 24.0.1274.0= 24.0.1275.0= 24.0.1276.0= 24.0.1276.1= 24.0.1277.0= 24.0.1278.0= 24.0.1279.0= 24.0.1280.0= 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 Google Chrome versionNavigate to Chrome menu > Help > About Google Chrome, or navigate to chrome://version/ in the address bar. Note the version number displayed.Affected if The version is 24.0.1312.51 or earlier, OR matches one of these specific versions: 24.0.1272.0, 24.0.1272.1, 24.0.1273.0, 24.0.1274.0, 24.0.1275.0, 24.0.1276.0, 24.0.1276.1, 24.0.1277.0, 24.0.1278.0, 24.0.1279.0, or 24.0.1280.0
-
Check Chrome on openSUSERun 'rpm -q chrome' or 'rpm -q google-chrome' in the terminal to retrieve the installed package version.Affected if The installed version matches one of the vulnerable Chrome versions listed above for the openSUSE 12.1 or 12.2 releases.
-
Confirm DOM handling is in useThis is a DOM handling vulnerability. The flaw triggers when Chrome processes specific DOM operations. Usage of web content with dynamic DOM manipulation is required for exploitation.Affected if Chrome is actively used to browse untrusted or attacker-controlled web pages that could trigger the vulnerable DOM code path.
You are affected if you are running any Google Chrome version 24.0.1312.51 or below, including the specific versions 24.0.1272.0 through 24.0.1280.0, on openSUSE 12.1/12.2 or other platforms, and you use Chrome to browse the web where the vulnerable DOM handling code can be triggered.
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 24.0.1312.52 or later to remediate this 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-5147 — 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-5147 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