CVE-2012-2828: Integer Overflow
First published: Wed Jun 27 2012(Updated: )
Multiple integer overflows in the PDF functionality in Google Chrome before 20.0.1132.43 allow remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted document.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <=20.0.1132.42 | |
| Google Chrome (Trace Event) | =20.0.1132.0 | |
| Google Chrome (Trace Event) | =20.0.1132.1 | |
| Google Chrome (Trace Event) | =20.0.1132.2 | |
| Google Chrome (Trace Event) | =20.0.1132.3 | |
| Google Chrome (Trace Event) | =20.0.1132.4 | |
| Google Chrome (Trace Event) | =20.0.1132.5 | |
| Google Chrome (Trace Event) | =20.0.1132.6 | |
| Google Chrome (Trace Event) | =20.0.1132.7 | |
| Google Chrome (Trace Event) | =20.0.1132.8 | |
| Google Chrome (Trace Event) | =20.0.1132.9 | |
| Google Chrome (Trace Event) | =20.0.1132.10 | |
| Google Chrome (Trace Event) | =20.0.1132.11 | |
| Google Chrome (Trace Event) | =20.0.1132.12 | |
| Google Chrome (Trace Event) | =20.0.1132.13 | |
| Google Chrome (Trace Event) | =20.0.1132.14 | |
| Google Chrome (Trace Event) | =20.0.1132.15 | |
| Google Chrome (Trace Event) | =20.0.1132.16 | |
| Google Chrome (Trace Event) | =20.0.1132.17 | |
| Google Chrome (Trace Event) | =20.0.1132.18 | |
| Google Chrome (Trace Event) | =20.0.1132.19 | |
| Google Chrome (Trace Event) | =20.0.1132.20 | |
| Google Chrome (Trace Event) | =20.0.1132.21 | |
| Google Chrome (Trace Event) | =20.0.1132.22 | |
| Google Chrome (Trace Event) | =20.0.1132.23 | |
| Google Chrome (Trace Event) | =20.0.1132.24 | |
| Google Chrome (Trace Event) | =20.0.1132.25 | |
| Google Chrome (Trace Event) | =20.0.1132.26 | |
| Google Chrome (Trace Event) | =20.0.1132.27 | |
| Google Chrome (Trace Event) | =20.0.1132.28 | |
| Google Chrome (Trace Event) | =20.0.1132.29 | |
| Google Chrome (Trace Event) | =20.0.1132.30 | |
| Google Chrome (Trace Event) | =20.0.1132.31 | |
| Google Chrome (Trace Event) | =20.0.1132.32 | |
| Google Chrome (Trace Event) | =20.0.1132.33 | |
| Google Chrome (Trace Event) | =20.0.1132.34 | |
| Google Chrome (Trace Event) | =20.0.1132.35 | |
| Google Chrome (Trace Event) | =20.0.1132.36 | |
| Google Chrome (Trace Event) | =20.0.1132.37 | |
| Google Chrome (Trace Event) | =20.0.1132.38 | |
| Google Chrome (Trace Event) | =20.0.1132.39 | |
| Google Chrome (Trace Event) | =20.0.1132.40 | |
| Google Chrome (Trace Event) | =20.0.1132.41 |
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
Frequently Asked Questions
What is the severity of CVE-2012-2828?
CVE-2012-2828 has a medium severity, as it can lead to denial of service attacks.
How do I fix CVE-2012-2828?
To fix CVE-2012-2828, you should update Google Chrome to version 20.0.1132.43 or later.
What are the effects of CVE-2012-2828?
CVE-2012-2828 may allow remote attackers to cause a denial of service or potentially other unspecified impacts.
Which versions of Google Chrome are affected by CVE-2012-2828?
CVE-2012-2828 affects Google Chrome versions up to and including 20.0.1132.42.
Is CVE-2012-2828 still a concern for current users?
As long as users have updated to Google Chrome version 20.0.1132.43 or later, CVE-2012-2828 is no longer a concern.
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/last-modified-date
- agent/author
- agent/weakness
- agent/severity
- agent/references
- 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)/20.0.1132.42
- version/google chrome (trace event)/20.0.1132.0
- version/google chrome (trace event)/20.0.1132.1
- version/google chrome (trace event)/20.0.1132.2
- version/google chrome (trace event)/20.0.1132.3
- version/google chrome (trace event)/20.0.1132.4
- version/google chrome (trace event)/20.0.1132.5
- version/google chrome (trace event)/20.0.1132.6
- version/google chrome (trace event)/20.0.1132.7
- version/google chrome (trace event)/20.0.1132.8
- version/google chrome (trace event)/20.0.1132.9
- version/google chrome (trace event)/20.0.1132.10
- version/google chrome (trace event)/20.0.1132.11
- version/google chrome (trace event)/20.0.1132.12
- version/google chrome (trace event)/20.0.1132.13
- version/google chrome (trace event)/20.0.1132.14
- version/google chrome (trace event)/20.0.1132.15
- version/google chrome (trace event)/20.0.1132.16
- version/google chrome (trace event)/20.0.1132.17
- version/google chrome (trace event)/20.0.1132.18
- version/google chrome (trace event)/20.0.1132.19
- version/google chrome (trace event)/20.0.1132.20
- version/google chrome (trace event)/20.0.1132.21
- version/google chrome (trace event)/20.0.1132.22
- version/google chrome (trace event)/20.0.1132.23
- version/google chrome (trace event)/20.0.1132.24
- version/google chrome (trace event)/20.0.1132.25
- version/google chrome (trace event)/20.0.1132.26
- version/google chrome (trace event)/20.0.1132.27
- version/google chrome (trace event)/20.0.1132.28
- version/google chrome (trace event)/20.0.1132.29
- version/google chrome (trace event)/20.0.1132.30
- version/google chrome (trace event)/20.0.1132.31
- version/google chrome (trace event)/20.0.1132.32
- version/google chrome (trace event)/20.0.1132.33
- version/google chrome (trace event)/20.0.1132.34
- version/google chrome (trace event)/20.0.1132.35
- version/google chrome (trace event)/20.0.1132.36
- version/google chrome (trace event)/20.0.1132.37
- version/google chrome (trace event)/20.0.1132.38
- version/google chrome (trace event)/20.0.1132.39
- version/google chrome (trace event)/20.0.1132.40
- version/google chrome (trace event)/20.0.1132.41