VDB

CVE-2017-5130

CVE-2017-5130 PUBLISHED CVSS 8.800000190734863 HIGH

Reported by chrome · Published February 7, 2018

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.

Risk scores

CVSS 3.0
8.800000190734863
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
n/aGoogle Chrome prior to 62.0.3202.62Google Chrome prior to 62.0.3202.62
n/aGoogle Chrome prior to 62.0.3202.6262.0.3202.62
archchromium0
NuGetlibxml20

Timeline

  • Oct 18, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Jan 27, 2026 CVE Updated
  • Mar 17, 2026 Security Advisory (5 in total, the first dated here)
  • Mar 18, 2026 Distribution Patch (2 in total, the first dated here)
  • Sep 29, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-5130
vulnetix vdb fixes CVE-2017-5130

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-5130/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›