CVE-2011-2802 json
Google V8, as used in Google Chrome before 13.0.782.107, does not properly perform const lookups, which allows remote attackers to cause a…
published 2011-08-03 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2776
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Google V8, as used in Google Chrome before 13.0.782.107, does not properly perform const lookups, which allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted web site.
Patch / fix
- google chrome 13.0.782.107
Exploit prediction
1.03% chance of exploitation in the next 30 days, higher than 63% 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-20 Improper Input Validation
- Technology feeds
References
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14236
vdb-entry, signature
- googlechromereleases.blogspot.com /2011/08/stable-channel-update.html
-
osvdb.org
/74253
vdb-entry
- code.google.com /p/chromium/issues/detail?id=88591
-
exchange.xforce.ibmcloud.com
/vulnerabilities/68964
vdb-entry
Sources
- CVE List CVE-2011-2802
- NVD CVE-2011-2802
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.