Bug 1724459
| Summary: | bzip2: out-of-bounds write in function BZ2_decompress | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Dhananjay Arunesh <darunesh> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | aileenc, apmukher, chazlett, cwarfiel, drieden, ggaughan, gmalinko, jamartis, janstey, jaromir.capik, jcalhoun, jchaloup, jochrist, mjw, pdelbell, phil, rstepani, scorneli |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
An out-of-bounds memory access vulnerability in the bzip2 package exists such that nSelectors is used in a loop from 0 to nSelectors to access selectorMtf,
so if nSelectors is bigger than BZ_MAX_SELECTORS it'll do an out-of-bounds memory access.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-27 10:45:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1724462, 1728163, 1728164 | ||
| Bug Blocks: | 1724461 | ||
|
Description
Dhananjay Arunesh
2019-06-27 07:16:35 UTC
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. This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:8922 https://access.redhat.com/errata/RHSA-2024:8922 (In reply to Stefan Cornelius from comment #2) > 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. Correct. It is a bogus CVE. The issue is harmless. The patch does break decompression of some .bz2 files. Running the upstream testsuite will show the patch causes some files to not decompress anymore. Upstream did fix it differently: https://inbox.sourceware.org/bzip2-devel/f9230fc65a3529b59b31f13494c72a1c01a6148e.camel@klomp.org/ https://sourceware.org/cgit/bzip2/commit/?id=b07b105d1b66e32760095e3602261738443b9e13 Complete analysis from 2019: https://gnu.wildebeest.org/blog/mjw/2019/08/02/bzip2-and-the-cve-that-wasnt/ Upstream reminder today to Please don't "fix" CVE-2019-12900: https://inbox.sourceware.org/bzip2-devel/20241108214034.GC8315@gnu.wildebeest.org This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2024:10803 https://access.redhat.com/errata/RHSA-2024:10803 |