DescriptionThe xz_decomp function in xzlib.c in libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035.
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)
NVD severitylow

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
libxml2 (PTS)stretch2.9.4+dfsg1-2.2+deb9u2fixed
stretch (security)2.9.4+dfsg1-2.2+deb9u3fixed
bullseye, sid2.9.10+dfsg-6fixed

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

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
libxml2source(unstable)(not affected)


- libxml2 <not-affected> (Fix for CVE-2017-18258 not applied, cf. bug #895195)
Fixed by:
Before upstream commit
the memlimit argument to lzma_auto_decoder was set to UINT64_MAX, possibly
allowing a malicious LZMA compressed files to consume large amounts of memory
when decompressed. Setting memlimit to UINT64_MAX the limiter is effectively
disabled and "lzma_auto_decoder(&state->strm, UINT64_MAX, 0)" can never result
in LZMA_MEMLIMIT_ERROR outcome because there is no way to exceed UINT64_MAX.
Thus CVE-2018-9251 is only affecting libxml2 if e2a9122b8dde53d320750451e9907a7dcb2ca8bb
is applied.

Search for package or bug name: Reporting problems