CVE-2012-2875
First published: Wed Sep 26 2012(Updated: )
Multiple unspecified vulnerabilities in the PDF functionality in Google Chrome before 22.0.1229.79 allow remote attackers to have an unknown impact via a crafted document.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <=22.0.1229.78 | |
| Google Chrome (Trace Event) | =22.0.1229.0 | |
| Google Chrome (Trace Event) | =22.0.1229.1 | |
| Google Chrome (Trace Event) | =22.0.1229.2 | |
| Google Chrome (Trace Event) | =22.0.1229.3 | |
| Google Chrome (Trace Event) | =22.0.1229.4 | |
| Google Chrome (Trace Event) | =22.0.1229.6 | |
| Google Chrome (Trace Event) | =22.0.1229.7 | |
| Google Chrome (Trace Event) | =22.0.1229.8 | |
| Google Chrome (Trace Event) | =22.0.1229.9 | |
| Google Chrome (Trace Event) | =22.0.1229.10 | |
| Google Chrome (Trace Event) | =22.0.1229.11 | |
| Google Chrome (Trace Event) | =22.0.1229.12 | |
| Google Chrome (Trace Event) | =22.0.1229.14 | |
| Google Chrome (Trace Event) | =22.0.1229.16 | |
| Google Chrome (Trace Event) | =22.0.1229.17 | |
| Google Chrome (Trace Event) | =22.0.1229.18 | |
| Google Chrome (Trace Event) | =22.0.1229.20 | |
| Google Chrome (Trace Event) | =22.0.1229.21 | |
| Google Chrome (Trace Event) | =22.0.1229.22 | |
| Google Chrome (Trace Event) | =22.0.1229.23 | |
| Google Chrome (Trace Event) | =22.0.1229.24 | |
| Google Chrome (Trace Event) | =22.0.1229.25 | |
| Google Chrome (Trace Event) | =22.0.1229.26 | |
| Google Chrome (Trace Event) | =22.0.1229.27 | |
| Google Chrome (Trace Event) | =22.0.1229.28 | |
| Google Chrome (Trace Event) | =22.0.1229.29 | |
| Google Chrome (Trace Event) | =22.0.1229.31 | |
| Google Chrome (Trace Event) | =22.0.1229.32 | |
| Google Chrome (Trace Event) | =22.0.1229.33 | |
| Google Chrome (Trace Event) | =22.0.1229.35 | |
| Google Chrome (Trace Event) | =22.0.1229.36 | |
| Google Chrome (Trace Event) | =22.0.1229.37 | |
| Google Chrome (Trace Event) | =22.0.1229.39 | |
| Google Chrome (Trace Event) | =22.0.1229.48 | |
| Google Chrome (Trace Event) | =22.0.1229.49 | |
| Google Chrome (Trace Event) | =22.0.1229.50 | |
| Google Chrome (Trace Event) | =22.0.1229.51 | |
| Google Chrome (Trace Event) | =22.0.1229.52 | |
| Google Chrome (Trace Event) | =22.0.1229.53 | |
| Google Chrome (Trace Event) | =22.0.1229.54 | |
| Google Chrome (Trace Event) | =22.0.1229.55 | |
| Google Chrome (Trace Event) | =22.0.1229.56 | |
| Google Chrome (Trace Event) | =22.0.1229.57 | |
| Google Chrome (Trace Event) | =22.0.1229.58 | |
| Google Chrome (Trace Event) | =22.0.1229.59 | |
| Google Chrome (Trace Event) | =22.0.1229.60 | |
| Google Chrome (Trace Event) | =22.0.1229.62 | |
| Google Chrome (Trace Event) | =22.0.1229.63 | |
| Google Chrome (Trace Event) | =22.0.1229.64 | |
| Google Chrome (Trace Event) | =22.0.1229.65 | |
| Google Chrome (Trace Event) | =22.0.1229.67 | |
| Google Chrome (Trace Event) | =22.0.1229.76 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://googlechromereleases.blogspot.com/2012/09/stable-channel-update_25.html
- https://code.google.com/p/chromium/issues/detail?id=134955
- https://code.google.com/p/chromium/issues/detail?id=135488
- https://code.google.com/p/chromium/issues/detail?id=137106
- https://code.google.com/p/chromium/issues/detail?id=137288
- https://code.google.com/p/chromium/issues/detail?id=137302
- https://code.google.com/p/chromium/issues/detail?id=137547
- https://code.google.com/p/chromium/issues/detail?id=137556
- https://code.google.com/p/chromium/issues/detail?id=137606
- https://code.google.com/p/chromium/issues/detail?id=137635
- https://code.google.com/p/chromium/issues/detail?id=137880
- https://code.google.com/p/chromium/issues/detail?id=137928
- https://code.google.com/p/chromium/issues/detail?id=144579
- https://code.google.com/p/chromium/issues/detail?id=145079
- https://code.google.com/p/chromium/issues/detail?id=145121
- https://code.google.com/p/chromium/issues/detail?id=145163
- https://code.google.com/p/chromium/issues/detail?id=146462
- https://exchange.xforce.ibmcloud.com/vulnerabilities/78836
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15627
Frequently Asked Questions
What is the severity of CVE-2012-2875?
The severity of CVE-2012-2875 is classified as high due to the potential for remote code execution through crafted PDF documents.
How do I fix CVE-2012-2875?
To fix CVE-2012-2875, update Google Chrome to version 22.0.1229.79 or later.
What types of attacks can exploit CVE-2012-2875?
CVE-2012-2875 can be exploited through specially crafted PDF documents that may trigger arbitrary code execution.
Which versions of Google Chrome are affected by CVE-2012-2875?
CVE-2012-2875 affects Google Chrome versions prior to 22.0.1229.79.
Is there a workaround for CVE-2012-2875?
There is no specific workaround for CVE-2012-2875 other than updating to a secure version of Google Chrome.
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/references
- agent/author
- agent/severity
- agent/tags
- agent/description
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/22.0.1229.78
- version/google chrome (trace event)/22.0.1229.0
- version/google chrome (trace event)/22.0.1229.1
- version/google chrome (trace event)/22.0.1229.2
- version/google chrome (trace event)/22.0.1229.3
- version/google chrome (trace event)/22.0.1229.4
- version/google chrome (trace event)/22.0.1229.6
- version/google chrome (trace event)/22.0.1229.7
- version/google chrome (trace event)/22.0.1229.8
- version/google chrome (trace event)/22.0.1229.9
- version/google chrome (trace event)/22.0.1229.10
- version/google chrome (trace event)/22.0.1229.11
- version/google chrome (trace event)/22.0.1229.12
- version/google chrome (trace event)/22.0.1229.14
- version/google chrome (trace event)/22.0.1229.16
- version/google chrome (trace event)/22.0.1229.17
- version/google chrome (trace event)/22.0.1229.18
- version/google chrome (trace event)/22.0.1229.20
- version/google chrome (trace event)/22.0.1229.21
- version/google chrome (trace event)/22.0.1229.22
- version/google chrome (trace event)/22.0.1229.23
- version/google chrome (trace event)/22.0.1229.24
- version/google chrome (trace event)/22.0.1229.25
- version/google chrome (trace event)/22.0.1229.26
- version/google chrome (trace event)/22.0.1229.27
- version/google chrome (trace event)/22.0.1229.28
- version/google chrome (trace event)/22.0.1229.29
- version/google chrome (trace event)/22.0.1229.31
- version/google chrome (trace event)/22.0.1229.32
- version/google chrome (trace event)/22.0.1229.33
- version/google chrome (trace event)/22.0.1229.35
- version/google chrome (trace event)/22.0.1229.36
- version/google chrome (trace event)/22.0.1229.37
- version/google chrome (trace event)/22.0.1229.39
- version/google chrome (trace event)/22.0.1229.48
- version/google chrome (trace event)/22.0.1229.49
- version/google chrome (trace event)/22.0.1229.50
- version/google chrome (trace event)/22.0.1229.51
- version/google chrome (trace event)/22.0.1229.52
- version/google chrome (trace event)/22.0.1229.53
- version/google chrome (trace event)/22.0.1229.54
- version/google chrome (trace event)/22.0.1229.55
- version/google chrome (trace event)/22.0.1229.56
- version/google chrome (trace event)/22.0.1229.57
- version/google chrome (trace event)/22.0.1229.58
- version/google chrome (trace event)/22.0.1229.59
- version/google chrome (trace event)/22.0.1229.60
- version/google chrome (trace event)/22.0.1229.62
- version/google chrome (trace event)/22.0.1229.63
- version/google chrome (trace event)/22.0.1229.64
- version/google chrome (trace event)/22.0.1229.65
- version/google chrome (trace event)/22.0.1229.67
- version/google chrome (trace event)/22.0.1229.76