critical
9.3
CWE
94
Advisory Published
Updated

CVE-2010-0647: Code Injection

First published: Thu Feb 18 2010(Updated: )

WebKit before r53525, as used in Google Chrome before 4.0.249.89, allows remote attackers to execute arbitrary code in the Chrome sandbox via a malformed RUBY element, as demonstrated by a <ruby>><table><rt> sequence.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
WebKit<=r53475
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

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-0647?

    CVE-2010-0647 is classified as a high-severity vulnerability that allows remote code execution.

  • How do I fix CVE-2010-0647?

    To fix CVE-2010-0647, update your browser to a version newer than Google Chrome 4.0.249.89 or Apple WebKit r53525.

  • Who is affected by CVE-2010-0647?

    CVE-2010-0647 affects users of Google Chrome versions prior to 4.0.249.89 and Apple WebKit versions up to r53475.

  • What type of attack is associated with CVE-2010-0647?

    CVE-2010-0647 is associated with remote attacks that exploit a vulnerability in processing malformed RUBY elements in web documents.

  • When was CVE-2010-0647 disclosed?

    CVE-2010-0647 was disclosed in January 2010.

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