ChromeWeb browser · Google
CVE-2012-5146
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 · uneditedGoogle Chrome before 24.0.1312.52 allows remote attackers to bypass the Same Origin Policy via a malformed URL.
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 confidenceThis is a client-side Same Origin Policy (SOP) bypass vulnerability in Google Chrome browsers prior to version 24.0.1312.52. Attackers could exploit malformed URLs to circumvent the SOP security mechanism, potentially allowing malicious web pages to access data from other origins they should be restricted from reading.
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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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.
-
Determine installed Google Chrome versionOpen Chrome, click the menu icon (three dots) > Help > About Google Chrome, or navigate to chrome://version/ in the address bar. Record the version number displayed.Affected if The version displayed 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 version via command line (Windows)Open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v VersionAffected if The returned version value falls within the affected range listed above
-
Check Chrome version via command line (Mac)Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The returned version number is in the affected range
-
Check Chrome version on Linux (if applicable)Open Terminal and run: google-chrome --version or chrome --versionAffected if The returned version number is in the affected range
-
Verify Chrome auto-update statusIn Chrome, navigate to chrome://settings/help and scroll to the 'Update' section. Check if updates are enabled and note the last update check date.Affected if Updates are disabled or the browser has not been updated to version 24.0.1312.52 or later
You are affected if the installed Google Chrome version is 24.0.1312.51 or lower, or matches any of the specific vulnerable point versions listed, meaning the Same Origin Policy bypass could be exploited in your environment.
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 patch the vulnerability. Organizations should ensure automated browser updates are enabled or deploy the updated browser version enterprise-wide.
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-5146 — 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-5146 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