ChromeWeb browser · Google
CVE-2017-5029
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 · uneditedThe xsltAddTextString function in transform.c in libxslt 1.1.29, as used in Blink in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android, lacked a check for integer overflow during a size calculation, which allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page.
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 in xsltAddTextString function in libxslt 1.1.29 during size calculation allows remote attackers to perform out-of-bounds memory writes via crafted HTML pages. The function fails to properly validate size calculations before allocating memory, leading to heap corruption when processing malicious XSLT content.
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
<= 57.0.2987.75<= 57.0.2987.100
Debian LinuxOperating system
= 8.0= 9.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0= 1.1.29CVSS 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 Google Chrome version on desktop systemsNavigate to chrome://settings/help or run 'google-chrome --version' in terminalAffected if Version is 57.0.2987.75 or earlier, or 57.0.2987.76 through 57.0.2987.100 (these versions are vulnerable)
-
Check libxslt library versionRun 'xsltproc --version' or check the installed libxslt package version via package manager (dpkg -l libxslt or rpm -q libxslt)Affected if Version is exactly 1.1.29 (this specific version is vulnerable)
-
Identify if XSLT processing is in useSearch application logs, code, or configuration for XSLT transformation usage (look for .xsl/.xslt file processing, xsltproc usage, or programmatic XSLT transforms in applications)Affected if Any application processes XSLT stylesheets from untrusted sources, enabling the vulnerable code path
-
Check Chrome for Android versionOpen Chrome app, go to Settings > About ChromeAffected if Version is 57.0.2987.107 or earlier (vulnerable on Android)
A user is affected if they run Chrome version 57.0.2987.100 or earlier (desktop) or 57.0.2987.107 or earlier (Android), OR have libxslt 1.1.29 installed and process XSLT content.
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 dataUpdate Google Chrome to version 57.0.2987.98 (or later) for desktop platforms and 57.0.2987.108 for Android. For systems using libxslt directly, update to a patched version of libxslt that includes integer overflow protection.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5029 — 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-5029 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