8.8
CWE
119 787 190
Advisory Published
CVE Published
Updated

CVE-2017-5130: Buffer Overflow

First published: Tue Sep 12 2017(Updated: )

libxml2. A buffer overflow issue was addressed with improved memory handling.

Credit: an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher an anonymous researcher chrome-cve-admin@google.com

Affected SoftwareAffected VersionHow to fix
Apple iCloud for Windows<7.0
7.0
Apple iTunes for Windows<12.7
12.7
Google Chrome<62.0.3202.62
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Xmlsoft Libxml2<2.9.5
Apple watchOS<4
4
Apple tvOS<11
11
Apple iOS<11
11
redhat/chromium-browser<62.0.3202.62
62.0.3202.62
Apple macOS<10.13
10.13
Apple macOS<10.13.1
10.13.1
Apple Sierra
Apple El Capitan

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.

Parent vulnerabilities

(Appears in the following advisories)

Peer vulnerabilities

(Found alongside the following vulnerabilities)

Frequently Asked Questions

  • What is CVE-2017-5130?

    CVE-2017-5130 is a buffer overflow vulnerability in libxml2.

  • Which products are affected by CVE-2017-5130?

    Products such as Apple tvOS 11, Google Chrome up to 62.0.3202.62, Debian Linux 8.0 and 9.0, libxml2 up to 2.9.5, iTunes for Windows up to 12.7, watchOS up to 4, iCloud for Windows up to 7.0, Red Hat Chromium Browser up to 62.0.3202.62, Apple macOS High Sierra up to 10.13.1, Apple Sierra, Apple El Capitan, and Apple iOS up to 11 are affected by CVE-2017-5130.

  • What is the severity of CVE-2017-5130?

    CVE-2017-5130 has a severity rating of 8.8 out of 10.0.

  • How can CVE-2017-5130 be exploited?

    CVE-2017-5130 can be potentially exploited by a remote attacker via a crafted XML file, leading to heap corruption.

  • Are there any remediation measures available for CVE-2017-5130?

    Yes, various remedies have been provided by different vendors and products to fix CVE-2017-5130. It is recommended to refer to the vendor-specific advisories and update to the latest patched versions as suggested.

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