CVE-2011-2855 json
Google Chrome before 14.0.835.163 does not properly handle Cascading Style Sheets (CSS) token sequences, which allows remote attackers to c…
published 2011-09-17 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2829
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Google 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."
Patch / fix
- google chrome 14.0.835.163
- apple itunes 10.6
- apple safari 5.1.4
- apple iphone_os 5.1
Exploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
- Technology feeds
References
-
lists.apple.com
/archives/security-announce/2012/Mar/msg00003.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2012/Mar/msg00000.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2012/Mar/msg00001.html
vendor-advisory
-
osvdb.org
/75557
vdb-entry
- code.google.com /p/chromium/issues/detail?id=92959
-
exchange.xforce.ibmcloud.com
/vulnerabilities/69882
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14485
vdb-entry, signature
-
securitytracker.com
/id?1026774
vdb-entry
-
secunia.com
/advisories/48377
third-party-advisory
- googlechromereleases.blogspot.com /2011/09/stable-channel-update_16.html
-
secunia.com
/advisories/48274
third-party-advisory
-
secunia.com
/advisories/48288
third-party-advisory
Sources
- CVE List CVE-2011-2855
- NVD CVE-2011-2855
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.