CVE-2011-2787 json
Google Chrome before 13.0.782.107 does not properly address re-entrancy issues associated with the GPU lock, which allows remote attackers…
published 2011-08-03 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2761
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Google Chrome before 13.0.782.107 does not properly address re-entrancy issues associated with the GPU lock, which allows remote attackers to cause a denial of service (application crash) via unspecified vectors.
Patch / fix
- google chrome 13.0.782.107
Exploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14533
vdb-entry, signature
-
osvdb.org
/74237
vdb-entry
- googlechromereleases.blogspot.com /2011/08/stable-channel-update.html
- code.google.com /p/chromium/issues/detail?id=84805
-
exchange.xforce.ibmcloud.com
/vulnerabilities/68949
vdb-entry
Sources
- CVE List CVE-2011-2787
- NVD CVE-2011-2787
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.