medium
4.3
CWE
119
Advisory Published
Updated

CVE-2010-4008: Buffer Overflow

First published: Tue Nov 16 2010(Updated: )

libxml2 before 2.7.8, as used in Google Chrome before 7.0.517.44, Apple Safari 5.0.2 and earlier, and other products, reads from invalid memory locations during processing of malformed XPath expressions, which allows context-dependent attackers to cause a denial of service (application crash) via a crafted XML document.

Credit: product-security@apple.com

Affected SoftwareAffected VersionHow to fix
Google Chrome<7.0.517.44
iOS<4.2
Apple iOS and macOS<10.6.7
Apple iTunes for Windows<10.2
Apple Mobile Safari<5.0.4
libxml2<2.7.8
Debian=5.0
Debian=6.0
Ubuntu=10.10
Ubuntu=6.06
Ubuntu=8.04
Ubuntu=10.04
Ubuntu=9.10
redhat enterprise Linux desktop=6.0
redhat enterprise Linux server=6.0
redhat enterprise Linux workstation=6.0
redhat enterprise Linux server eus=6.3
openSUSE=11.1
openSUSE=11.2
openSUSE=11.3
SUSE Linux Enterprise Server=11-sp1
SUSE Linux Enterprise Server=11
SUSE Linux Enterprise Server=10-sp3
Apache OpenOffice>=2.0.0<=2.4.3
Apache OpenOffice>=3.0.0<3.3.0

Remedy

http://code.google.com/p/chromium/issues/detail?id=58731

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

    CVE-2010-4008 has a severity rating that indicates it could lead to a denial of service due to application crashes.

  • How do I fix CVE-2010-4008?

    To fix CVE-2010-4008, update the affected software to versions higher than libxml2 2.7.8, Google Chrome 7.0.517.44, and Apple Safari 5.0.2.

  • What products are affected by CVE-2010-4008?

    CVE-2010-4008 affects multiple products, including Google Chrome, Apple Safari, Apple iTunes, and libxml2 prior to 2.7.8.

  • Can CVE-2010-4008 cause data loss?

    CVE-2010-4008 primarily causes application crashes, which can lead to data loss if unsaved work is present at the time of the crash.

  • Is there a workaround for CVE-2010-4008?

    There is no officially recommended workaround for CVE-2010-4008 aside from applying the necessary software updates.

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