CVE-2011-1813 json
Google Chrome before 12.0.742.91 does not properly implement the framework for extensions, which allows remote attackers to cause a denial…
published 2011-06-09 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1811
- cvss
- 6.8
- 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 71%
- public exploits
- 0
- none known
Summary
Google Chrome before 12.0.742.91 does not properly implement the framework for extensions, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that lead to a "stale pointer."
Patch / fix
- google chrome 12.0.742.91
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% 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
-
secunia.com
/advisories/44829
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/67896
vdb-entry
- code.google.com /p/chromium/issues/detail?id=78516
- googlechromereleases.blogspot.com /2011/06/chrome-stable-release.html
-
osvdb.org
/72783
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14481
vdb-entry, signature
-
securityfocus.com
/bid/48129
vdb-entry
Sources
- CVE List CVE-2011-1813
- NVD CVE-2011-1813
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.