CVE-2017-5130

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.

Published: 2018-02-07 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2017-5130 is rated Moderate Risk (64.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.77%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-5130

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-02 2.98% 2.77% -0.21%
2 2026-06-16 3.09% 2.98% -0.11%
3 2026-06-15 3.09%

Full EPSS history (25 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5130

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-5130

OS Trackers for CVE-2017-5130

vendor priority summary link
debian not yet assigned CVE-2017-5130 not yet assigned priority: Debian including 1 source packages (libxml2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-5130
gentoo normal CVE-2017-5130: 1 GLSA(s) (201710-24), 2 atom(s) (www-client/chromium, www-client/google-chrome); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-5130
redhat high https://access.redhat.com/security/cve/CVE-2017-5130
suse medium CVE-2017-5130 severity moderate: SUSE including 42 source package names (0.9.1:libxml2-2-2.9.4-46.12.1, 1.0.0:libxml2-2-2.9.4-46.12.1, …), 132 product×package rows across 65 product lines (Container caasp/v4/default-http-backend, Container caasp/v4/dnsmasq-nanny, … (65 product lines)): Fixed 132. https://www.suse.com/security/cve/CVE-2017-5130/
ubuntu negligible CVE-2017-5130 negligible priority: Ubuntu including 3 source packages (chromium-browser, libxml2, oxide-qt), 21 status rows across 7 suites (artful, bionic, cosmic, trusty, upstream, xenial, zesty): released 10, ignored 7, DNE 3, needs-triage 1. https://ubuntu.com/security/CVE-2017-5130

Affected software / configurations for CVE-2017-5130

Vendor Product Version Raw CPE
google chrome < 62.0.3202.62 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
xmlsoft libxml2 < 2.9.5 cpe:2.3:a:xmlsoft:libxml2:*:*:*:*:*:*:*:*

References for CVE-2017-5130

URL Tags
http://bugzilla.gnome.org/show_bug.cgi?id=783026 Issue Tracking
http://www.securityfocus.com/bid/101482 Third Party Advisory VDB Entry
https://access.redhat.com/errata/RHSA-2017:2997 Third Party Advisory
https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html Vendor Advisory
https://crbug.com/722079 Third Party Advisory
https://git.gnome.org/browse/libxml2/commit/?id=897dffbae322b46b83f99a607d527058a72c51ed Third Party Advisory
https://lists.debian.org/debian-lts-announce/2017/11/msg00034.html Third Party Advisory
https://lists.debian.org/debian-lts-announce/2022/04/msg00004.html
https://security.gentoo.org/glsa/201710-24 Third Party Advisory
https://security.netapp.com/advisory/ntap-20190719-0001/
https://www.oracle.com/security-alerts/cpuapr2020.html
cvelogic Threat Intelligence