ChromeWeb browser · Google
CVE-2012-2869
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 21.0.1180.89 does not properly load URLs, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger a "stale buffer."
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 21.0.1180.89 contains a stale buffer vulnerability in its URL loading functionality that allows remote attackers to cause a denial of service or potentially achieve unspecified other impact via specially crafted vectors.
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
<= 21.0.1180.88= 21.0.1180.0= 21.0.1180.1= 21.0.1180.2= 21.0.1180.31= 21.0.1180.32= 21.0.1180.33= 21.0.1180.34= 21.0.1180.35= 21.0.1180.36= 21.0.1180.37= 21.0.1180.38= 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 if Google Chrome is installedLook for Chrome executable: on Windows check Program Files/Google/Chrome/Application/chrome.exe, on Linux check /usr/bin/google-chrome or /opt/google/chrome/google-chromeAffected if Chrome is present on the system
-
Determine installed Chrome versionRun 'google-chrome --version' or 'chrome --version' from command line, or open Chrome and navigate to chrome://version to view the full version stringAffected if Version number is 21.0.1180.x where x is 0 through 88 (any version <= 21.0.1180.88)
-
Confirm version is within affected rangeCompare the installed version number against the affected list: 21.0.1180.0 through 21.0.1180.38 are explicitly listed, plus any version <= 21.0.1180.88Affected if Installed version matches 21.0.1180.x where x is between 0 and 88 inclusive, or version is unknown but appears to be Chrome 21.0.1180.x series
-
Verify URL loading feature usageThe vulnerability is in URL loading functionality; confirm the browser is used to navigate to web URLs (this is the default behavior)Affected if Chrome is used to load or navigate to any URLs (standard browser use)
-
Check openSUSE system package if applicableOn openSUSE 12.1 or 12.2, check installed Chrome package via 'rpm -qa | grep chrome' or package managerAffected if Running openSUSE 12.1 or 12.2 with Google Chrome installed from system packages
A user is affected if Google Chrome version 21.0.1180.x (where x is 0-88) is installed and used to load URLs, with the highest risk on openSUSE 12.1 and 12.2 systems.
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 21.0.1180.89 or later to patch the stale buffer vulnerability in URL loading.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-2869 — 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-2869 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