Name | CVE-2019-12900 |
Description | BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more) |
References | DLA-1833-1, DLA-1953-1 |
NVD severity | high |
Debian Bugs | 930886, 934359 |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
bzip2 (PTS) | stretch | 1.0.6-8.1 | vulnerable |
| buster | 1.0.6-9.2~deb10u1 | fixed |
| bullseye, sid | 1.0.8-4 | fixed |
clamav (PTS) | stretch | 0.102.3+dfsg-0~deb9u1 | fixed |
| stretch (security) | 0.102.4+dfsg-0+deb9u1 | fixed |
| buster | 0.102.4+dfsg-0+deb10u1 | fixed |
| bullseye, sid | 0.103.0+dfsg-3 | fixed |
The information below is based on the following data on fixed versions.
Notes
[stretch] - bzip2 <no-dsa> (Not exploitable; potential dangerous parts already guarded)
https://gitlab.com/federicomenaquintero/bzip2/commit/74de1e2e6ffc9d51ef9824db71a8ffee5962cdbc
The original fix introduces regressions when extracting certain lbzip2 files
which were created with a buggy libzip2: https://bugs.debian.org/931278
Details on followup: https://sourceware.org/ml/bzip2-devel/2019-q3/msg00007.html
explaining as well why, whilst the issue described by CVE-2019-12900 is definitvely
an issue, it was not exploitable in the first place.
Regression fix: https://sourceware.org/git/?p=bzip2.git;a=commit;h=b07b105d1b66e32760095e3602261738443b9e13
Clamav: https://blog.clamav.net/2019/08/clamav-01014-security-patch-release-has.html
clamav uses libbz2 but the "nsis" scanner/decompressor has a decompress.c from bzip2