CVE-2012-1845 in the critical feed json
Use-after-free vulnerability in Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the DEP and ASLR protection mechani…
published 2012-03-22 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1855
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.8%
- EPSS 4.8% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the DEP and ASLR protection mechanisms, and execute arbitrary code, via unspecified vectors, as demonstrated by VUPEN during a Pwn2Own competition at CanSecWest 2012. NOTE: the primary affected product may be clarified later; it was not identified by the researcher, who reportedly stated "it really doesn't matter if it's third-party code."
Exploit prediction
4.79% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
pwn2own.zerodayinitiative.com
/status.html
not-applicable, third-party-advisory, vdb-entry
-
forbes.com
/sites/andygreenberg/2012/03/21/meet-the-hackers-who-sell-spies-the-tools-to-crack-your-pc-and-get-paid-six-fi
press/media-coverage
-
exchange.xforce.ibmcloud.com
/vulnerabilities/74323
vdb-entry, third-party-advisory
-
zdnet.com
/blog/security/pwn2own-2012-google-chrome-browser-sandbox-first-to-fall/10588
press/media-coverage
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14843
vdb-entry, signature, third-party-advisory
-
twitter.com
/vupen/statuses/177576000761237505
broken-link
Sources
- CVE List CVE-2012-1845
- NVD CVE-2012-1845
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.