Vulnerabilities · 2017 · Google
CVE-2017-5130
Google Chrome vulnerability
An integer overflow in xmlmemory.c in libxml2 before 2.9.5, as used in Google Chrome prior to 62.0.3202.62 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted XML file.
Affected products
Chrome, Debian Linux, Libxml2. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html · Vendor Advisory
- www.securityfocus.com/bid/101482 · Third Party Advisory
- access.redhat.com/errata/RHSA-2017:2997 · Third Party Advisory
- crbug.com/722079 · Third Party Advisory
- git.gnome.org/browse/libxml2/commit/?id=897dffbae322b46b83f99a607d527058a72c51ed · Third Party Advisory
- lists.debian.org/debian-lts-announce/2017/11/msg00034.html · Third Party Advisory
- security.gentoo.org/glsa/201710-24 · Third Party Advisory
- bugzilla.gnome.org/show_bug.cgi?id=783026
- nvd.nist.gov/vuln/detail/CVE-2017-5130
- cve.org/CVERecord?id=CVE-2017-5130
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.