| Name | CVE-2017-5130 |
| Description | 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-1188-1, DLA-2972-1, ELA-837-1 |
| Debian Bugs | 880000 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| chromium-browser (PTS) | jessie, jessie (lts) | 57.0.2987.98-1~deb8u1 | vulnerable |
| stretch (security), stretch (lts), stretch | 71.0.3578.80-1~deb9u1 | fixed | |
| libxml2 (PTS) | jessie, jessie (lts) | 2.9.1+dfsg1-5+deb8u17 | fixed |
| stretch (security) | 2.9.4+dfsg1-2.2+deb9u7 | vulnerable | |
| stretch (lts), stretch | 2.9.4+dfsg1-2.2+deb9u11 | fixed | |
| buster, buster (lts) | 2.9.4+dfsg1-7+deb10u9 | fixed | |
| buster (security) | 2.9.4+dfsg1-7+deb10u6 | fixed | |
| bullseye | 2.9.10+dfsg-6.7+deb11u4 | fixed | |
| bullseye (security) | 2.9.10+dfsg-6.7+deb11u5 | fixed | |
| bookworm | 2.9.14+dfsg-1.3~deb12u1 | fixed | |
| sid, trixie | 2.12.7+dfsg+really2.9.14-0.2 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| chromium-browser | source | (unstable) | 62.0.3202.75-1 | unimportant | ||
| libxml2 | source | wheezy | 2.8.0+dfsg1-7+wheezy10 | DLA-1188-1 | ||
| libxml2 | source | jessie | 2.9.1+dfsg1-5+deb8u15 | ELA-837-1 | ||
| libxml2 | source | stretch | 2.9.4+dfsg1-2.2+deb9u10 | ELA-837-1 | ||
| libxml2 | source | (unstable) | 2.9.4+dfsg1-5.1 | 880000 |
[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://gitlab.gnome.org/GNOME/libxml2/-/commit/897dffbae322b46b83f99a607d527058a72c51ed
Needs follow up: https://gitlab.gnome.org/GNOME/libxml2/-/commit/ed48d65b4d6c5cec7be035ad5eebeba873b4b955