ChromeWeb browser · Google
CVE-2011-1191
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 10.0.648.127 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the handling of DOM URLs.
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 confidenceA use-after-free vulnerability in Google Chrome versions prior to 10.0.648.127 exists in the component responsible for handling DOM URLs. The vulnerability occurs when memory associated with a DOM URL object is freed but the browser continues to reference it, potentially allowing remote attackers to execute arbitrary code or cause a denial of service through specially crafted web pages.
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
< 10.0.648.127CVSS 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 installed Chrome version via browser UIOpen Google Chrome, click the wrench icon (or three-dot menu in newer versions), then select Help > About Google Chrome. The version number will be displayed on that page.Affected if The displayed version is less than 10.0.648.127 (for example, 10.0.648.100 or any version 9.x or earlier).
-
Check Chrome version via address barType chrome://version in the Chrome address bar and press Enter. The first line shows the installed version.Affected if The version number shown is lower than 10.0.648.127.
-
Check Chrome version via command line (Windows)Open Command Prompt and run: reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v versionAffected if The version value returned is less than 10.0.648.127.
-
Check Chrome version via command line (Linux)Open a terminal and run: google-chrome --version or chromium --versionAffected if The version output is lower than 10.0.648.127.
-
Check Chrome version via command line (Mac)Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The version output is lower than 10.0.648.127.
You are affected if the installed Google Chrome version is any release prior to 10.0.648.127.
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 data10.0.648.127
Upgrade Google Chrome to version 10.0.648.127 or later. For web applications that may trigger this vulnerability, implement Content Security Policy headers and avoid relying on specific DOM URL behaviors that could expose users.
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-2011-1191 — 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-2011-1191 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