critical
9.3
CWE
189 190
Advisory Published
Updated

CVE-2010-0649: Integer Overflow

First published: Thu Feb 18 2010(Updated: )

Integer overflow in the CrossCallParamsEx::CreateFromBuffer function in sandbox/src/crosscall_server.cc in Google Chrome before 4.0.249.89 allows attackers to leverage renderer access to cause a denial of service (heap memory corruption) or possibly have unspecified other impact via a malformed message, related to deserializing of sandbox messages.

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.78
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.78
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/02/stable-channel-update.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-0649?

    CVE-2010-0649 has a medium severity rating due to potential heap memory corruption and denial of service conditions.

  • How do I fix CVE-2010-0649?

    To fix CVE-2010-0649, users should update Google Chrome to version 4.0.249.89 or later.

  • What impact can CVE-2010-0649 have on my system?

    CVE-2010-0649 can lead to denial of service conditions, potentially allowing attackers to crash the affected application.

  • Which versions of Google Chrome are affected by CVE-2010-0649?

    CVE-2010-0649 affects Google Chrome versions prior to 4.0.249.89, including early beta releases.

  • Is exploiting CVE-2010-0649 difficult for attackers?

    Exploiting CVE-2010-0649 may require some technical knowledge, but the vulnerability poses a risk through rendered web content.

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