ChromeWeb browser · Google
CVE-2017-5130
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInteger overflow vulnerability in xmlmemory.c in libxml2 before version 2.9.5 allows remote attackers to exploit heap corruption via specially crafted XML files. This affects Google Chrome prior to 62.0.3202.62 and other products using the vulnerable libxml2 library.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 62.0.3202.62
Debian LinuxOperating system
= 8.0= 9.0< 2.9.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed libxml2 version on Linux systemsRun 'rpm -q libxml2' on RHEL/CentOS or 'dpkg -l libxml2' on Debian/Ubuntu to retrieve the installed package versionAffected if The reported version is lower than 2.9.5
-
Check Google Chrome versionOpen Chrome and navigate to 'chrome://version' or run 'google-chrome --version' from command lineAffected if The Chrome version is lower than 62.0.3202.62
-
Verify if applications depend on libxml2 for XML parsingRun 'ldd <application_binary> | grep libxml' or check package dependencies to see if a given application links against libxml2Affected if The application uses a vulnerable libxml2 version (below 2.9.5) for XML processing
-
Check Debian Linux version for packaged libxml2Run 'cat /etc/debian_version' to identify the Debian release, then cross-reference with the affected Debian 8.0 or 9.0 releasesAffected if Running Debian 8.0 or 9.0 with the unpatched libxml2 package installed
A system is affected if it runs libxml2 versions below 2.9.5, Chrome versions below 62.0.3202.62, or Debian 8.0/9.0 with the vulnerable libxml2 package, and processes untrusted XML content through the vulnerable code path.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.9.562.0.3202.62
Update libxml2 to version 2.9.5 or later. For Chrome users, update to version 62.0.3202.62 or later. Sanitize and validate XML input to reduce attack surface.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data