Skip to content
Fencer Intel
high 8.8

CVE-2017-5029 json

Nokogiri implementation of libxslt lacks integer overflow checks

published 2017-04-24 9 y ago modified 2026-06-17 4 mo ago also GHSA-pf6m-fxpq-fg8v , EUVD-2018-0301

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

The 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.

Patch / fix

  • rubygems nokogiri 1.7.2
  • libxslt Debian 14, Debian 13, Debian 12 1.1.29-2.1

debian advisories DEBIAN-CVE-2017-5029

  • libxslt Ubuntu 14.04 LTS 1.1.28-2ubuntu0.1
  • libxslt Ubuntu 16.04 LTS 1.1.28-2.1ubuntu0.1
  • oxide-qt Ubuntu 14.04 LTS 1.21.5-0ubuntu0.14.04.1
  • oxide-qt Ubuntu 16.04 LTS 1.21.5-0ubuntu0.16.04.1
  • chromium-browser Ubuntu 14.04 LTS 58.0.3029.81-0ubuntu0.14.04.1172
  • chromium-browser Ubuntu 16.04 LTS 57.0.2987.98-0ubuntu0.16.04.1276

ubuntu advisories UBUNTU-CVE-2017-5029

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium-browser RHEL 6 EXTRAS 57.0.2987.98-1.el6

red hat advisories RHSA-2017:0499

  • libxslt SLES for SAP 12 SP2, SLES for SAP 12 SP1, SLES for Raspberry Pi 12 SP2 +6 more 1.1.28-16.1
  • libxslt SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 1.1.24-19.33.1
  • libxslt-python SLE Software Development Kit 11 SP4 1.1.24-19.33.3

suse advisories SUSE-SU-2017:1313-1SUSE-SU-2017:1282-1

  • rubygem-nokogiri openSUSE Tumbleweed 1.18.9-1.4
  • rubygem-nokogiri openSUSE Tumbleweed 1.18.2-1.1
  • rubygem-nokogiri openSUSE Tumbleweed 1.15.5-1.5
  • libxslt openSUSE Tumbleweed 1.1.34-3.2
  • rubygem-nokogiri openSUSE Tumbleweed 1.13.3-1.1
  • ruby3.2-rubygem-nokogiri openSUSE Tumbleweed 1.13.9-1.7
  • chromium Package Hub 12 SP2 57.0.2987.98-8.1

opensuse advisories openSUSE-SU-2026:10356-1openSUSE-SU-2025:14697-1openSUSE-SU-2024:14174-1openSUSE-SU-2024:11017-1openSUSE-SU-2024:11912-1openSUSE-SU-2024:13165-1

  • libxslt Alpine 3.24, Alpine 3.23, Alpine 3.22 +20 more 1.1.29-r1

alpine advisories ALPINE-CVE-2017-5029

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libxslt Arch Linux 1.1.29+41+gdf5330d1-1
  • chromium Arch Linux 57.0.2987.98-1

arch linux advisories AVG-195AVG-197

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-5029 updated cvss 8.8

chromium-browser: integer overflow in libxslt

  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 57.0.2987.98-1.el6 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 57.0.2987.98-1.el6 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 57.0.2987.98-1.el6
    fixed: vendor fix RHSA-2017:0499

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.53% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
rubygems nokogiri
<1.7.2
1.7.2

Affected products

  • n/a Google Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.