CVE-2011-3111 json
Google V8, as used in Google Chrome before 19.0.1084.52, allows remote attackers to cause a denial of service (invalid read operation) via…
published 2012-05-24 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3079
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Google V8, as used in Google Chrome before 19.0.1084.52, allows remote attackers to cause a denial of service (invalid read operation) via unspecified vectors.
Patch / fix
- google chrome 19.0.1084.52
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-3111 updated cvss 4.3
v8: DoS via unspecified vectors
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
security.gentoo.org
/glsa/glsa-201205-04.xml
vendor-advisory
-
googlechromereleases.blogspot.com
/2012/05/stable-channel-update_23.html
vendor-advisory
-
securityfocus.com
/bid/53679
vdb-entry
-
securitytracker.com
/id?1027098
vdb-entry
-
secunia.com
/advisories/49306
third-party-advisory
-
secunia.com
/advisories/49277
third-party-advisory
- code.google.com /p/chromium/issues/detail?id=126414
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15549
vdb-entry, signature
Sources
- CVE List CVE-2011-3111
- NVD CVE-2011-3111
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.