dbcve.org
ChromeWeb browser · Google

CVE-2012-5122

HIGH · 7.5 CVSS v2.0 Published 2012-11-07
Fix available
A fix is available. Upgrade to after 23.0.1271.62 or later.
See remediation →
84/100
Remediation priority · High
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 23.0.1271.64 does not properly perform a cast of an unspecified variable during handling of input, which allows remote attackers to cause a denial of service or possibly have other impact via unknown 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 · moderate confidence

Type confusion vulnerability in Google Chrome before 23.0.1271.64 where an unspecified variable is improperly cast during input handling, allowing remote attackers to cause denial of service or potentially execute arbitrary code via crafted input.

MitigationUpdate Google Chrome to version 23.0.1271.64 or later to apply the patched build.

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:<= 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.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Chrome version
    Open chrome://version in the Chrome browser address bar and note the version number displayed, or run 'google-chrome --version' from command line
    Affected if The version shown is 23.0.1271.62 or lower, or falls within 23.0.1271.0 through 23.0.1271.10 inclusive
  2. Confirm full version string
    On chrome://version page, verify the full version line (e.g., 23.0.1271.62) rather than just the major release number
    Affected if The full version matches any of the affected versions listed in the CVE (23.0.1271.0 through 23.0.1271.62, excluding .64 and later)
  3. Check if this is a stable release channel
    Navigate to chrome://settings and scroll to 'About Chrome' to see the update status, or check the channel via chrome://chrome URL
    Affected if The browser is on Stable, Beta, or Dev channel running an affected version - all channels with versions before 23.0.1271.64 are potentially vulnerable

You are affected if your installed Google Chrome version is 23.0.1271.62 or earlier, or any version from 23.0.1271.0 through 23.0.1271.10 inclusive; the fix was released in version 23.0.1271.64.

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 23.0.1271.62
Interim mitigation

Update Google Chrome to version 23.0.1271.64 or later to apply the patched build.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-5122 — 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-5122 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