CVE-2010-0659 in the critical feed json
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 allocat…
published 16y ago modified 4mo ago also EUVD-2010-0690
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2010-0659 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.19% chance of exploitation in the next 30 days, higher than 88% 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-399 Resource Management Errors
- Technology feeds
References
-
googlechromereleases.blogspot.com
/2010/01/stable-channel-update_25.html
patch
-
lists.opensuse.org
/opensuse-security-announce/2011-01/msg00006.html
vendor-advisory
-
sites.google.com
/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
vendor-advisory
-
secunia.com
/advisories/43068
third-party-advisory
- trac.webkit.org /changeset/52833
-
vupen.com
/english/advisories/2011/0212
vdb-entry
- bugs.webkit.org /show_bug.cgi?id=33231
-
securitytracker.com
/id?1023506
vdb-entry
- code.google.com /p/chromium/issues/detail?id=28566
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14079
vdb-entry, signature
Sources
- CVE List CVE-2010-0659
- NVD CVE-2010-0659
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.