CVE-2011-2875 json
Google V8, as used in Google Chrome before 14.0.835.163, does not properly perform object sealing, which allows remote attackers to cause a…
published 2011-09-17 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2849
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Google V8, as used in Google Chrome before 14.0.835.163, does not properly perform object sealing, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage "type confusion."
Patch / fix
- google chrome 14.0.835.163
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% 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-843 Access of Resource Using Incompatible Type
- Technology feeds
References
- code.google.com /p/chromium/issues/detail?id=95920
-
osvdb.org
/75554
vdb-entry
- googlechromereleases.blogspot.com /2011/09/stable-channel-update_16.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14229
vdb-entry, signature
-
exchange.xforce.ibmcloud.com
/vulnerabilities/69893
vdb-entry
Sources
- CVE List CVE-2011-2875
- NVD CVE-2011-2875
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.