CVE-2011-1119 json
Google Chrome before 9.0.597.107 does not properly determine device orientation, which allows remote attackers to cause a denial of service…
published 2011-03-01 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1133
- cvss
- 7.5
- 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 Chrome before 9.0.597.107 does not properly determine device orientation, 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 9.0.597.107
Exploit prediction
1.50% 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 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
googlechromereleases.blogspot.com
/2011/02/stable-channel-update_28.html
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/65737
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/46614
vdb-entry, third-party-advisory
-
code.google.com
/p/chromium/issues/detail?id=71595
permissions-required
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14542
vdb-entry, signature, third-party-advisory
Sources
- CVE List CVE-2011-1119
- NVD CVE-2011-1119
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.