ChromeWeb browser · Google
CVE-2012-5145
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 SVG layout.
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 confidenceA use-after-free vulnerability in Google Chrome versions prior to 24.0.1312.52 allows remote attackers to trigger memory corruption through specially crafted SVG layout vectors. The vulnerability occurs when the browser fails to properly manage memory during SVG rendering, potentially allowing arbitrary code execution or denial of service.
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 installed Google Chrome versionOpen Google Chrome, click the menu icon (three dots) in the upper right corner, select Help, then select About Google Chrome. The version number is displayed on that page. Alternatively, navigate to chrome://version in the address bar.Affected if The displayed version is 24.0.1312.51 or lower, OR matches exactly any of these 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 OpenSUSE system version if applicableOn OpenSUSE Linux systems, open a terminal and run 'cat /etc/os-release' to display the system version information.Affected if The system is running OpenSUSE 12.1 or 12.2 with Google Chrome installed from any repository
-
Verify SVG rendering is activeThe vulnerability is triggered through SVG layout vectors. This occurs automatically when the browser renders any webpage containing SVG content. SVG support is built into Chrome by default and requires no special configuration.Affected if The browser renders any SVG content while running an affected version listed above
You are affected if your Google Chrome version falls within 24.0.1272.0 through 24.0.1280.0 or is 24.0.1312.51 or lower, especially on OpenSUSE 12.1 or 12.2 systems, 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 24.0.1312.52 or later to address the vulnerability. Organizations should ensure all end-user workstations have the latest browser version deployed.
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-5145 — 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-5145 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