ChromeWeb browser · Google
CVE-2011-2855
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 14.0.835.163 does not properly handle Cascading Style Sheets (CSS) token sequences, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that lead to a "stale node."
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 confidenceGoogle Chrome before 14.0.835.163 contains a flaw in its CSS parsing logic where token sequences are not handled properly, leading to a stale node condition in memory that can cause denial of service or potentially allow unspecified other impact.
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
< 14.0.835.163
SafariWeb browser
< 5.1.4< 10.6< 5.1CVSS 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.
-
Check if Google Chrome is installedOn Windows: Check for chrome.exe in Program Files or via registry. On macOS: Check /Applications/Google Chrome.app. On Linux: check for google-chrome in /usr/bin/ or /opt/Affected if Chrome is installed and version is less than 14.0.835.163
-
Determine installed Chrome versionLaunch Chrome, go to Help > About Google Chrome, or navigate to chrome://version, or run 'google-chrome --version' from command lineAffected if Version displayed is below 14.0.835.163
-
Check if Apple Safari is installedOn macOS: Check /Applications/Safari.app. On Windows: Check Program Files for Safari. Verify version via Safari > About Safari or Help > About SafariAffected if Safari is installed and version is below 5.1.4
-
Check if Apple iTunes is installedOn Windows: Check Program Files/iTunes or via Add/Remove Programs. On Mac: Check /Applications/iTunes.app. Get version from iTunes > About iTunesAffected if iTunes is installed and version is below 10.6
-
Check if iOS device is presentConnect iPhone/iPad to computer and check iTunes device summary, or check device Settings > General > About > VersionAffected if iOS version is below 5.1 (Note: iPhone OS was renamed to iOS starting with version 5)
You are affected if any of Chrome < 14.0.835.163, Safari < 5.1.4, iTunes < 10.6, or iOS < 5.1 is installed and the browser parses CSS content (which is default behavior).
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 data5.15.1.410.6
Update Google Chrome to version 14.0.835.163 or later. Organizations should deploy the update via their endpoint management systems and verify successful installation across managed endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2855 — 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-2855 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