ChromeWeb browser · Google
CVE-2012-5125
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 23.0.1271.64 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the handling of extension tabs.
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 23.0.1271.64 allows remote attackers to trigger memory corruption through specially crafted web content involving extension tabs, 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
<= 23.0.1271.62= 23.0.1271.0= 23.0.1271.1= 23.0.1271.2= 23.0.1271.3= 23.0.1271.4= 23.0.1271.5= 23.0.1271.6= 23.0.1271.7= 23.0.1271.8= 23.0.1271.9= 23.0.1271.10CVSS 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 if Google Chrome is installedOn Windows, check for Chrome in Program Files or via Registry. On macOS, check /Applications/Google Chrome.app. On Linux, run 'which google-chrome' or 'which chromium-browser'.Affected if Google Chrome is not found on the system, so this CVE does not apply.
-
Determine the installed Chrome versionOpen Google Chrome, click the menu icon, select 'Help' then 'About Google Chrome', or navigate to chrome://settings/help. Note the version number displayed.Affected if The displayed version is 23.0.1271.0 through 23.0.1271.10, or any version <= 23.0.1271.62.
-
Verify the specific vulnerable versionIf the version starts with 23.0.1271., confirm it is one of the explicitly affected builds: .0, .1, .2, .3, .4, .5, .6, .7, .8, .9, or .10.Affected if The version matches exactly one of the listed affected builds.
-
Check if extension tabs feature is relevantThe vulnerability involves extension tabs. Determine if Chrome extensions are enabled and in use by visiting chrome://extensions.Affected if Extensions are enabled and the Chrome version falls within the affected range, making exploitation possible through specially crafted web content.
You are affected if Google Chrome version 23.0.1271.0 through 23.0.1271.10 (or any version <= 23.0.1271.62) is installed and extensions are enabled, as the use-after-free flaw in extension tab handling 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 dataUpgrade Google Chrome to version 23.0.1271.64 or later. In enterprise environments, deploy the update via patch management and verify completion across all endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5125 — 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-5125 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