CVE-2011-0472 in the critical feed json
Google Chrome before 8.0.552.237 and Chrome OS before 8.0.552.344 do not properly handle the printing of PDF documents, which allows user-a…
published 2011-01-14 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0492
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Google Chrome before 8.0.552.237 and Chrome OS before 8.0.552.344 do not properly handle the printing of PDF documents, which allows user-assisted remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a multi-page document.
Patch / fix
- google chrome 8.0.552.237
- google chrome_os 8.0.552.344
Exploit prediction
2.19% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- code.google.com http://code.google.com/p/chromium/issues/detail?id=66334 referenced PoC, tagged "exploit" by a source, unverified
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
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=66334
exploit, issue-tracking, vendor-advisory
-
googlechromereleases.blogspot.com
/2011/01/chrome-stable-release.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14622
vdb-entry, signature, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64663
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/45788
vdb-entry, third-party-advisory
-
srware.net
/forum/viewtopic.php?f=18&t=2054
third-party-advisory
-
osvdb.org
/70455
vdb-entry, broken-link
-
secunia.com
/advisories/42951
third-party-advisory
Sources
- CVE List CVE-2011-0472
- NVD CVE-2011-0472
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.