CVE-2011-2348 json
Google V8, as used in Google Chrome before 12.0.742.112, performs an incorrect bounds check, which allows remote attackers to cause a denia…
published 2011-06-29 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2337
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
Google V8, as used in Google Chrome before 12.0.742.112, performs an incorrect bounds check, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
Patch / fix
- google chrome 12.0.742.112
Exploit prediction
1.47% chance of exploitation in the next 30 days, higher than 74% 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
- googlechromereleases.blogspot.com /2011/06/stable-channel-update_28.html
-
secunia.com
/advisories/45097
third-party-advisory
-
securitytracker.com
/id?1025730
vdb-entry
- code.google.com /p/chromium/issues/detail?id=85177
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14324
vdb-entry, signature
Sources
- CVE List CVE-2011-2348
- NVD CVE-2011-2348
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.