Security update for rage-encryption SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2024:3404-1 Final 1 1 2024-09-23T13:56:03Z current 2024-09-23T13:56:03Z 2024-09-23T13:56:03Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for rage-encryption This update for rage-encryption fixes the following issues: - Update to version 0.10.0 - CVE-2024-43806: Fixed rustix::fs::Dir iterator with the linux_raw backend that can cause memory exhaustion. (bsc#1229959) The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2024-3404,SUSE-SLE-Module-Basesystem-15-SP5-2024-3404,SUSE-SLE-Module-Basesystem-15-SP6-2024-3404,openSUSE-SLE-15.5-2024-3404,openSUSE-SLE-15.6-2024-3404 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2024/suse-su-20243404-1/ Link for SUSE-SU-2024:3404-1 https://lists.suse.com/pipermail/sle-security-updates/2024-September/019502.html E-Mail link for SUSE-SU-2024:3404-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1229959 SUSE Bug 1229959 https://www.suse.com/security/cve/CVE-2024-43806/ SUSE CVE CVE-2024-43806 page SUSE Linux Enterprise Module for Basesystem 15 SP5 SUSE Linux Enterprise Module for Basesystem 15 SP6 openSUSE Leap 15.5 openSUSE Leap 15.6 rage-encryption-0.10.0+0-150500.3.6.1 rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 rage-encryption-fish-completion-0.10.0+0-150500.3.6.1 rage-encryption-zsh-completion-0.10.0+0-150500.3.6.1 rage-encryption-0.10.0+0-150500.3.6.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP5 rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP5 rage-encryption-0.10.0+0-150500.3.6.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP6 rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 as a component of SUSE Linux Enterprise Module for Basesystem 15 SP6 rage-encryption-0.10.0+0-150500.3.6.1 as a component of openSUSE Leap 15.5 rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 as a component of openSUSE Leap 15.5 rage-encryption-0.10.0+0-150500.3.6.1 as a component of openSUSE Leap 15.6 rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 as a component of openSUSE Leap 15.6 rage-encryption-fish-completion-0.10.0+0-150500.3.6.1 as a component of openSUSE Leap 15.6 rage-encryption-zsh-completion-0.10.0+0-150500.3.6.1 as a component of openSUSE Leap 15.6 Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to "get stuck" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux's various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue. CVE-2024-43806 SUSE Linux Enterprise Module for Basesystem 15 SP5:rage-encryption-0.10.0+0-150500.3.6.1 SUSE Linux Enterprise Module for Basesystem 15 SP5:rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 SUSE Linux Enterprise Module for Basesystem 15 SP6:rage-encryption-0.10.0+0-150500.3.6.1 SUSE Linux Enterprise Module for Basesystem 15 SP6:rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 openSUSE Leap 15.5:rage-encryption-0.10.0+0-150500.3.6.1 openSUSE Leap 15.5:rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 openSUSE Leap 15.6:rage-encryption-0.10.0+0-150500.3.6.1 openSUSE Leap 15.6:rage-encryption-bash-completion-0.10.0+0-150500.3.6.1 openSUSE Leap 15.6:rage-encryption-fish-completion-0.10.0+0-150500.3.6.1 openSUSE Leap 15.6:rage-encryption-zsh-completion-0.10.0+0-150500.3.6.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20243404-1/ https://www.suse.com/security/cve/CVE-2024-43806.html CVE-2024-43806 https://bugzilla.suse.com/1229376 SUSE Bug 1229376