CVE-2017-5130

NameCVE-2017-5130
DescriptionAn 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.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)
ReferencesDLA-1188-1
NVD severitymedium (attack range: remote)
Debian Bugs880000

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
chromium-browser (PTS)jessie (security), jessie57.0.2987.98-1~deb8u1vulnerable
stretch63.0.3239.84-1~deb9u1fixed
stretch (security)68.0.3440.75-1~deb9u1fixed
buster, sid68.0.3440.75-2fixed
libxml2 (PTS)jessie (security), jessie2.9.1+dfsg1-5+deb8u6vulnerable
stretch (security), stretch2.9.4+dfsg1-2.2+deb9u2vulnerable
buster, sid2.9.4+dfsg1-7fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
chromium-browsersource(unstable)62.0.3202.75-1unimportant
libxml2source(unstable)2.9.4+dfsg1-5.1medium880000
libxml2sourcewheezy2.8.0+dfsg1-7+wheezy10mediumDLA-1188-1

Notes

[stretch] - libxml2 <no-dsa> (Minor issue)
[jessie] - libxml2 <no-dsa> (Minor issue)
chromium-browser uses system libxml2.
https://bugs.chromium.org/p/chromium/issues/detail?id=722079 (not public)
https://bugzilla.gnome.org/show_bug.cgi?id=783026 (not public)
xmlMemoryStrdup is only for debugging with excpetion in xmlint when invoked
with --maxmem. Similar issue for xmlMallocLoc and xmlReallocLoc.
Fixed by: https://git.gnome.org/browse/libxml2/commit/?id=897dffbae322b46b83f99a607d527058a72c51ed
Needs follow up: https://git.gnome.org/browse/libxml2/commit/?id=ed48d65b4d6c5cec7be035ad5eebeba873b4b955

Search for package or bug name: Reporting problems