BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors. Reference: https://gitlab.com/federicomenaquintero/bzip2/commit/74de1e2e6ffc9d51ef9824db71a8ffee5962cdbc
Created bzip2 tracking bugs for this issue: Affects: fedora-all [bug 1724462]
The patch causes a change in behavior, as certain files could now result in a CRC error, whereas they would previously decompress fine: https://sourceware.org/ml/bzip2-devel/2019-q2/msg00024.html https://gitlab.com/federicomenaquintero/bzip2/issues/24 I suppose that we follow upstream on whether or not we consider this a regression, as I'm rather indifferent on this matter. There does not seem to be a final decision from upstream on that yet. This also seems to be http://scary.beasts.org/security/CESA-2008-005.html Back then this was considered harmless due to the structure/buffer layout. As far as I can tell, this is still true.
Statement: This issue affects the versions of bzip2 as shipped with Red Hat Enterprise Linux 5, 6, 7, and 8. Red Hat Enterprise Linux 5 is now in Extended Life Phase of the support and maintenance life cycle. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Low, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat JBoss Fuse 7 uses a Java implemntation of bzip2, this is different to the bzip2 this vulnerability exists in.