critical
9.3
CWE
189 119 190
Advisory Published
CVE Published
Updated

CVE-2011-1944: Buffer Overflow

First published: Wed Jun 01 2011(Updated: )

An integer overflow, leading to heap-based buffer overflow was found in the way libxml, XML files manipulation library, processed certain XPath expressions. A remote attacker could provide a specially-crafted XML file, which once opened in an application linked against libxml would cause that application to crash, or, potentially, execute arbitrary code with the privileges of the user running the application. References: [1] <a href="http://scarybeastsecurity.blogspot.com/2011/05/libxml-vulnerability-and-interesting.html">http://scarybeastsecurity.blogspot.com/2011/05/libxml-vulnerability-and-interesting.html</a> [2] <a href="http://www.openwall.com/lists/oss-security/2011/05/31/5">http://www.openwall.com/lists/oss-security/2011/05/31/5</a> [3] <a href="http://www.openwall.com/lists/oss-security/2011/05/31/8">http://www.openwall.com/lists/oss-security/2011/05/31/8</a> Upstream patch: [4] <a href="http://git.gnome.org/browse/libxml2/commit/?id=d7958b21e7f8c447a26bb2436f08402b2c308be4">http://git.gnome.org/browse/libxml2/commit/?id=d7958b21e7f8c447a26bb2436f08402b2c308be4</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/libxml2<2.8.0
2.8.0
Gnome Libxml2=2.6.16
Gnome Libxml2=2.6.32
Gnome Libxml2=2.6.26
Gnome Libxml2=2.6.11
Gnome Libxml2=2.6.17
Gnome Libxml2=2.6.27
Gnome Libxml2=2.6.13
Gnome Libxml2=2.6.7
Gnome Libxml2=2.6.14
Gnome Libxml2=2.6.8
Gnome Libxml2=2.6.2
Gnome Libxml2=2.6.5
Gnome Libxml2=2.6.4
Gnome Libxml2=2.6.18
Gnome Libxml2=2.6.1
Gnome Libxml2=2.6.20
Gnome Libxml2=2.6.12
Gnome Libxml2=2.6.0
Gnome Libxml2=2.6.9
Gnome Libxml2=2.6.30
Gnome Libxml2=2.6.22
Gnome Libxml2=2.6.3
Gnome Libxml2=2.6.6
Gnome Libxml2=2.7.2
Gnome Libxml2=2.7.8
Gnome Libxml2=2.7.7
Gnome Libxml2=2.7.5
Gnome Libxml2=2.7.3
Gnome Libxml2=2.7.1
Gnome Libxml2=2.7.0
Gnome Libxml2=2.7.6
Gnome Libxml2=2.7.4
libxml2=1.8.9
libxml2=1.6.0
libxml2=1.7.2
libxml2=1.8.3
libxml2=1.8.0
libxml2=1.8.13
libxml2=1.8.10
libxml2=1.8.4
libxml2=1.8.6
libxml2=1.7.0
libxml2<=1.8.16
libxml2=1.8.14
libxml2=1.8.8
libxml2=1.7.4
libxml2=1.8.7
libxml2=1.7.3
libxml2=1.8.1
libxml2=1.8.11
libxml2=1.6.2
libxml2=1.5.0
libxml2=1.8.2
libxml2=1.8.12
libxml2=1.8.5
libxml2=1.6.1
libxml2=1.8.15
libxml2=1.7.1

Remedy

http://git.gnome.org/browse/libxml2/commit/?id=d7958b21e7f8c447a26bb2436f08402b2c308be4

Remedy

http://lists.fedoraproject.org/pipermail/package-announce/2011-July/062238.html

Remedy

http://scarybeastsecurity.blogspot.com/2011/05/libxml-vulnerability-and-interesting.html

Remedy

http://www.openwall.com/lists/oss-security/2011/05/31/8

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=709747

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-2011-1944?

    CVE-2011-1944 is considered a high severity vulnerability due to the potential for remote code execution and denial of service.

  • How do I fix CVE-2011-1944?

    To fix CVE-2011-1944, update libxml2 to version 2.8.0 or later.

  • What types of systems are affected by CVE-2011-1944?

    CVE-2011-1944 affects systems using libxml2 versions older than 2.8.0, including various distributions like Red Hat and Gnome.

  • What causes CVE-2011-1944?

    CVE-2011-1944 is caused by an integer overflow leading to a heap-based buffer overflow while processing specific XPath expressions in XML files.

  • Can CVE-2011-1944 be exploited remotely?

    Yes, an attacker can exploit CVE-2011-1944 remotely by providing a specially-crafted XML file that triggers the vulnerability.

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