CVE-2010-0663
Description
The ParamTraits<SkBitmap>::Read function in common/common_param_traits.cc in Google Chrome before 4.0.249.78 does not initialize the memory locations that will hold bitmap data, which might allow remote attackers to obtain potentially sensitive information from process memory by providing insufficient data, related to use of a (1) thumbnail database or (2) HTML canvas.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| chrome | 1.0.154.36 | | |
| chrome | 1.0.154.39 | | |
| chrome | 3.0.195.33 | | |
| chrome | 0.2.152.1 | | |
| chrome | 0.2.153.1 | | |
| chrome | 0.3.154.0 | | |
| chrome | 0.3.154.3 | | |
| chrome | 0.4.154.18 | | |
| chrome | 0.4.154.22 | | |
| chrome | 0.4.154.31 | | |
| chrome | 0.4.154.33 | | |
| chrome | 2.0.170.0 | | |
| chrome | 2.0.172 | | |
| chrome | 2.0.172.2 | | |
| chrome | 2.0.172.28 | | |
| chrome | 2.0.172.30 | | |
| chrome | 2.0.172.31 | | |
| chrome | 2.0.172.33 | | |
| chrome | 2.0.172.37 | | |
| chrome | 2.0.172.38 | | |
| chrome | 3.0.182.2 | | |
| chrome | 3.0.190.2 | | |
| chrome | 3.0.193.2 | | |
| chrome | {"endIncluding":"4.0.249.0"} | | |
| chrome | 0.2.149.27 | | |
| chrome | 0.2.149.29 | | |
| chrome | 0.2.149.30 | | |
| chrome | 1.0.154.48 | | |
| chrome | 1.0.154.52 | | |
| chrome | 1.0.154.53 | | |
| chrome | 1.0.154.59 | | |
| chrome | 1.0.154.65 | | |
| chrome | 2.0.156.1 | | |
| chrome | 2.0.157.0 | | |
| chrome | 2.0.172.8 | | |
| chrome | 2.0.172.27 | | |
| chrome | 2.0.157.2 | | |
| chrome | 2.0.158.0 | | |
| chrome | 2.0.159.0 | | |
| chrome | 2.0.169.0 | | |
| chrome | 2.0.169.1 | | |
| chrome | 3.0.195.21 | | |
| chrome | 3.0.195.24 | | |
| chrome | 3.0.195.32 | | |
| chrome | 1.0.154.42 | | |
| chrome | 1.0.154.43 | | |
| chrome | 1.0.154.46 | |
References
- http://code.google.com/p/chromium/issues/detail?id=31307
- http://googlechromereleases.blogspot.com/2010/01/stable-channel-update_25.html
- http://securitytracker.com/id?1023506
- http://sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14002
- http://code.google.com/p/chromium/issues/detail?id=31307
- http://googlechromereleases.blogspot.com/2010/01/stable-channel-update_25.html
- http://securitytracker.com/id?1023506
- http://sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14002
CWEs
CWE-200
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.