ChromeWeb browser · Google
CVE-2012-5136
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 23.0.1271.91 does not properly perform a cast of an unspecified variable during handling of the INPUT element, which allows remote attackers to cause a denial of service or possibly have unknown other impact via a crafted HTML document.
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 confidenceGoogle Chrome before version 23.0.1271.91 contains a vulnerability where an unspecified variable is improperly cast during INPUT element handling, allowing remote attackers to cause denial of service or potentially achieve unknown impact via crafted HTML documents.
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.89= 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= 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Verify Google Chrome is installedLocate the Chrome binary - on Linux check /usr/bin/google-chrome or /opt/google/chrome/google-chrome; on Windows check Program Files; or open Chrome and navigate to chrome://versionAffected if Google Chrome browser is present on the system
-
Determine the installed Google Chrome versionRun 'google-chrome --version' from command line, or open Chrome and go to chrome://version to view the full version stringAffected if Cannot determine version - Chrome may be installed but not accessible via command line
-
Compare installed version against affected rangeParse the version number from step 2 and compare against: 23.0.1271.0 through 23.0.1271.10, or any version <= 23.0.1271.89Affected if Installed version falls within 23.0.1271.0 to 23.0.1271.10 inclusive, or is 23.0.1271.89 or lower
-
Check openSUSE package version if applicableOn openSUSE systems, run 'rpm -q google-chrome' or 'zypper info google-chrome' to query the installed package versionAffected if openSUSE 12.1 or 12.2 with Google Chrome package version matching the affected range
User is affected if Google Chrome version is 23.0.1271.89 or lower, or exactly matches any version from 23.0.1271.0 through 23.0.1271.10.
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 23.0.1271.91 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-5136 — 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-5136 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