medium
5
CWE
200
Advisory Published
Updated

CVE-2010-0663: Infoleak

First published: Thu Feb 18 2010(Updated: )

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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Google Chrome (Trace Event)=2.0.172.8
Google Chrome (Trace Event)=0.3.154.3
Google Chrome (Trace Event)=3.0.182.2
Google Chrome (Trace Event)=0.2.149.30
Google Chrome (Trace Event)=0.4.154.31
Google Chrome (Trace Event)=1.0.154.39
Google Chrome (Trace Event)=2.0.172.38
Google Chrome (Trace Event)=1.0.154.59
Google Chrome (Trace Event)=0.2.149.27
Google Chrome (Trace Event)=1.0.154.53
Google Chrome (Trace Event)=0.4.154.33
Google Chrome (Trace Event)=2.0.170.0
Google Chrome (Trace Event)=1.0.154.43
Google Chrome (Trace Event)=1.0.154.42
Google Chrome (Trace Event)=2.0.169.1
Google Chrome (Trace Event)=2.0.172.33
Google Chrome (Trace Event)=3.0.195.24
Google Chrome (Trace Event)=3.0.195.33
Google Chrome (Trace Event)=1.0.154.52
Google Chrome (Trace Event)=2.0.172.27
Google Chrome (Trace Event)=1.0.154.65
Google Chrome (Trace Event)=2.0.157.2
Google Chrome (Trace Event)=0.4.154.18
Google Chrome (Trace Event)=0.2.149.29
Google Chrome (Trace Event)=2.0.157.0
Google Chrome (Trace Event)=0.2.152.1
Google Chrome (Trace Event)=0.3.154.0
Google Chrome (Trace Event)<=4.0.249.0
Google Chrome (Trace Event)=0.2.153.1
Google Chrome (Trace Event)=2.0.172.2
Google Chrome (Trace Event)=3.0.195.21
Google Chrome (Trace Event)=2.0.169.0
Google Chrome (Trace Event)=1.0.154.36
Google Chrome (Trace Event)=2.0.172
Google Chrome (Trace Event)=2.0.172.30
Google Chrome (Trace Event)=3.0.193.2-beta
Google Chrome (Trace Event)=2.0.156.1
Google Chrome (Trace Event)=3.0.195.32
Google Chrome (Trace Event)=1.0.154.46
Google Chrome (Trace Event)=3.0.190.2
Google Chrome (Trace Event)=0.4.154.22
Google Chrome (Trace Event)=2.0.159.0
Google Chrome (Trace Event)=2.0.158.0
Google Chrome (Trace Event)=2.0.172.28
Google Chrome (Trace Event)=2.0.172.31
Google Chrome (Trace Event)=1.0.154.48
Google Chrome (Trace Event)=2.0.172.37
Google Chrome<=4.0.249.0
Google Chrome=0.2.149.27
Google Chrome=0.2.149.29
Google Chrome=0.2.149.30
Google Chrome=0.2.152.1
Google Chrome=0.2.153.1
Google Chrome=0.3.154.0
Google Chrome=0.3.154.3
Google Chrome=0.4.154.18
Google Chrome=0.4.154.22
Google Chrome=0.4.154.31
Google Chrome=0.4.154.33
Google Chrome=1.0.154.36
Google Chrome=1.0.154.39
Google Chrome=1.0.154.42
Google Chrome=1.0.154.43
Google Chrome=1.0.154.46
Google Chrome=1.0.154.48
Google Chrome=1.0.154.52
Google Chrome=1.0.154.53
Google Chrome=1.0.154.59
Google Chrome=1.0.154.65
Google Chrome=2.0.156.1
Google Chrome=2.0.157.0
Google Chrome=2.0.157.2
Google Chrome=2.0.158.0
Google Chrome=2.0.159.0
Google Chrome=2.0.169.0
Google Chrome=2.0.169.1
Google Chrome=2.0.170.0
Google Chrome=2.0.172
Google Chrome=2.0.172.2
Google Chrome=2.0.172.8
Google Chrome=2.0.172.27
Google Chrome=2.0.172.28
Google Chrome=2.0.172.30
Google Chrome=2.0.172.31
Google Chrome=2.0.172.33
Google Chrome=2.0.172.37
Google Chrome=2.0.172.38
Google Chrome=3.0.182.2
Google Chrome=3.0.190.2
Google Chrome=3.0.193.2-beta
Google Chrome=3.0.195.21
Google Chrome=3.0.195.24
Google Chrome=3.0.195.32
Google Chrome=3.0.195.33

Remedy

http://googlechromereleases.blogspot.com/2010/01/stable-channel-update_25.html

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2010-0663?

    CVE-2010-0663 has been classified as a high severity vulnerability due to its potential for information disclosure.

  • How does CVE-2010-0663 affect users of Google Chrome?

    CVE-2010-0663 can allow remote attackers to access sensitive information from process memory by exploiting uninitialized memory locations in Chrome.

  • What versions of Google Chrome are affected by CVE-2010-0663?

    CVE-2010-0663 affects multiple versions of Google Chrome prior to 4.0.249.78, including versions 2.0 and 3.0.

  • How do I fix CVE-2010-0663?

    To fix CVE-2010-0663, users should upgrade to Google Chrome version 4.0.249.78 or later as it contains the necessary patches.

  • What should I do if I cannot update my version of Google Chrome affected by CVE-2010-0663?

    If updating is not possible, users should consider employing additional security measures such as using a different browser until they can upgrade.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203