CVE-2024-43806 `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion
An attacker can trigger unbounded memory allocation in the rustix library's directory iterator, causing an out-of-memory crash and denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-43806?
CVE-2024-43806 is a medium-severity denial of service vulnerability in bytecodealliance rustix, published on 26 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-400
Which versions are affected by CVE-2024-43806?
8 open source packages ship an affected version, including rustix.
| Package | Affected | Fixed in |
|---|---|---|
rustix crates.io | From 0.35.11 | 0.35.15 |
rustix crates.io | From 0.35.11 | 0.35.15 |
rustix crates.io | From 0.36.0 | 0.36.16 |
rustix crates.io | From 0.36.0 | 0.36.16 |
rustix crates.io | From 0.37.0 | 0.37.25 |
rustix crates.io | From 0.37.0 | 0.37.25 |
2 more packages
rustix crates.io | From 0.38.0 | 0.38.19 |
rustix crates.io | From 0.38.0 | 0.38.19 |
Linux distribution packages (6)
rage-encryption SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 0.10.0+0-150500.3.6.1 |
rage-encryption SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 0.10.0+0-150500.3.6.1 |
rage-encryption openSUSE:Leap 15.5 | All versions | 0.10.0+0-150500.3.6.1 |
rage-encryption openSUSE:Leap 15.6 | All versions | 0.10.0+0-150500.3.6.1 |
389-ds openSUSE:Tumbleweed | All versions | 3.1.1~git13.a9c7ff9-1.1 |
rage-encryption openSUSE:Tumbleweed | All versions | 0.10.0+0-3.1 |
How do I fix CVE-2024-43806?
Upgrade rustix to a fixed version for your release line: 0.35.15, 0.36.16, 0.37.25 or 0.38.19.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2024-43806 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43806 exists.
Sources
Also known as AZL-48300, AZL-48304, AZL-48312, AZL-48318, AZL-48324, AZL-48327 and 8 more.