CVE-2010-0659
First published: Thu Feb 18 2010(Updated: )
The image decoder in WebKit before r52833, as used in Google Chrome before 4.0.249.78, does not properly handle a failure of memory allocation, which allows remote attackers to execute arbitrary code in the Chrome sandbox via a malformed GIF file that specifies a large size.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WebKit | <=r53524 | |
| Google Chrome (Trace Event) | <=4.0.249.78 | |
| Google Chrome (Trace Event) | =0.2.149.27 | |
| Google Chrome (Trace Event) | =0.2.149.29 | |
| Google Chrome (Trace Event) | =0.2.149.30 | |
| Google Chrome (Trace Event) | =0.2.152.1 | |
| Google Chrome (Trace Event) | =0.2.153.1 | |
| Google Chrome (Trace Event) | =0.3.154.0 | |
| Google Chrome (Trace Event) | =0.3.154.3 | |
| Google Chrome (Trace Event) | =0.4.154.18 | |
| Google Chrome (Trace Event) | =0.4.154.22 | |
| Google Chrome (Trace Event) | =0.4.154.31 | |
| Google Chrome (Trace Event) | =0.4.154.33 | |
| Google Chrome (Trace Event) | =1.0.154.36 | |
| Google Chrome (Trace Event) | =1.0.154.39 | |
| Google Chrome (Trace Event) | =1.0.154.42 | |
| Google Chrome (Trace Event) | =1.0.154.43 | |
| Google Chrome (Trace Event) | =1.0.154.46 | |
| Google Chrome (Trace Event) | =1.0.154.48 | |
| Google Chrome (Trace Event) | =1.0.154.52 | |
| Google Chrome (Trace Event) | =1.0.154.53 | |
| Google Chrome (Trace Event) | =1.0.154.59 | |
| Google Chrome (Trace Event) | =1.0.154.65 | |
| Google Chrome (Trace Event) | =2.0.156.1 | |
| Google Chrome (Trace Event) | =2.0.157.0 | |
| Google Chrome (Trace Event) | =2.0.157.2 | |
| Google Chrome (Trace Event) | =2.0.158.0 | |
| Google Chrome (Trace Event) | =2.0.159.0 | |
| Google Chrome (Trace Event) | =2.0.169.0 | |
| Google Chrome (Trace Event) | =2.0.169.1 | |
| Google Chrome (Trace Event) | =2.0.170.0 | |
| Google Chrome (Trace Event) | =2.0.172 | |
| Google Chrome (Trace Event) | =2.0.172.2 | |
| Google Chrome (Trace Event) | =2.0.172.8 | |
| Google Chrome (Trace Event) | =2.0.172.27 | |
| Google Chrome (Trace Event) | =2.0.172.28 | |
| Google Chrome (Trace Event) | =2.0.172.30 | |
| Google Chrome (Trace Event) | =2.0.172.31 | |
| Google Chrome (Trace Event) | =2.0.172.33 | |
| Google Chrome (Trace Event) | =2.0.172.37 | |
| Google Chrome (Trace Event) | =2.0.172.38 | |
| Google Chrome (Trace Event) | =3.0.182.2 | |
| Google Chrome (Trace Event) | =3.0.190.2 | |
| Google Chrome (Trace Event) | =3.0.193.2-beta | |
| Google Chrome (Trace Event) | =3.0.195.21 | |
| Google Chrome (Trace Event) | =3.0.195.24 | |
| Google Chrome (Trace Event) | =3.0.195.32 | |
| Google Chrome (Trace Event) | =3.0.195.33 | |
| Google Chrome (Trace Event) | =4.0.244.0 |
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://code.google.com/p/chromium/issues/detail?id=28566
- http://trac.webkit.org/changeset/52833
- http://googlechromereleases.blogspot.com/2010/01/stable-channel-update_25.html
- http://sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
- http://securitytracker.com/id?1023506
- https://bugs.webkit.org/show_bug.cgi?id=33231
- http://lists.opensuse.org/opensuse-security-announce/2011-01/msg00006.html
- http://secunia.com/advisories/43068
- http://www.vupen.com/english/advisories/2011/0212
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14079
Frequently Asked Questions
What is the severity of CVE-2010-0659?
CVE-2010-0659 has been rated as a high severity vulnerability because it allows remote attackers to execute arbitrary code in the Chrome sandbox.
How do I fix CVE-2010-0659?
To fix CVE-2010-0659, you should update Google Chrome to version 4.0.249.78 or later.
What versions of Google Chrome are affected by CVE-2010-0659?
CVE-2010-0659 affects all versions of Google Chrome prior to 4.0.249.78.
What is the impact of CVE-2010-0659?
The impact of CVE-2010-0659 is that it can lead to arbitrary code execution, potentially compromising user data and security.
Is CVE-2010-0659 specific to any particular OS?
CVE-2010-0659 is not specific to any particular operating system as it affects the Chrome browser regardless of the underlying OS.
- collector/nvd-historical
- agent/type
- agent/references
- agent/author
- agent/weakness
- agent/severity
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/apple
- canonical/webkit
- version/webkit/r53524
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/4.0.249.78
- version/google chrome (trace event)/0.2.149.27
- version/google chrome (trace event)/0.2.149.29
- version/google chrome (trace event)/0.2.149.30
- version/google chrome (trace event)/0.2.152.1
- version/google chrome (trace event)/0.2.153.1
- version/google chrome (trace event)/0.3.154.0
- version/google chrome (trace event)/0.3.154.3
- version/google chrome (trace event)/0.4.154.18
- version/google chrome (trace event)/0.4.154.22
- version/google chrome (trace event)/0.4.154.31
- version/google chrome (trace event)/0.4.154.33
- version/google chrome (trace event)/1.0.154.36
- version/google chrome (trace event)/1.0.154.39
- version/google chrome (trace event)/1.0.154.42
- version/google chrome (trace event)/1.0.154.43
- version/google chrome (trace event)/1.0.154.46
- version/google chrome (trace event)/1.0.154.48
- version/google chrome (trace event)/1.0.154.52
- version/google chrome (trace event)/1.0.154.53
- version/google chrome (trace event)/1.0.154.59
- version/google chrome (trace event)/1.0.154.65
- version/google chrome (trace event)/2.0.156.1
- version/google chrome (trace event)/2.0.157.0
- version/google chrome (trace event)/2.0.157.2
- version/google chrome (trace event)/2.0.158.0
- version/google chrome (trace event)/2.0.159.0
- version/google chrome (trace event)/2.0.169.0
- version/google chrome (trace event)/2.0.169.1
- version/google chrome (trace event)/2.0.170.0
- version/google chrome (trace event)/2.0.172
- version/google chrome (trace event)/2.0.172.2
- version/google chrome (trace event)/2.0.172.8
- version/google chrome (trace event)/2.0.172.27
- version/google chrome (trace event)/2.0.172.28
- version/google chrome (trace event)/2.0.172.30
- version/google chrome (trace event)/2.0.172.31
- version/google chrome (trace event)/2.0.172.33
- version/google chrome (trace event)/2.0.172.37
- version/google chrome (trace event)/2.0.172.38
- version/google chrome (trace event)/3.0.182.2
- version/google chrome (trace event)/3.0.190.2
- version/google chrome (trace event)/3.0.193.2-beta
- version/google chrome (trace event)/3.0.195.21
- version/google chrome (trace event)/3.0.195.24
- version/google chrome (trace event)/3.0.195.32
- version/google chrome (trace event)/3.0.195.33
- version/google chrome (trace event)/4.0.244.0