Microsoft security update for CVE-2024-43806
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43806. This page also shows what EchelonGraph holds for CVE-2024-43806, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products16
- azl3 flux 0.194.5-2 on Azure Linux 3.0
- azl3 flux 0.194.5-4 on Azure Linux 3.0
- azl3 kata-containers 3.2.0.azl3-2 on Azure Linux 3.0
- azl3 kata-containers 3.2.0.azl4-1 on Azure Linux 3.0
- azl3 kata-containers-cc 3.2.0.azl3-1 on Azure Linux 3.0
- azl3 kata-containers-cc 3.2.0.azl4-1 on Azure Linux 3.0
- azl3 virtiofsd 1.8.0-3 on Azure Linux 3.0
- cbl2 cloud-hypervisor 32.0-7 on CBL Mariner 2.0
- cbl2 cloud-hypervisor 32.0-7 on CBL-Mariner 2.0
- cbl2 kata-containers-cc 3.2.0.azl2-7 on CBL Mariner 2.0
- cbl2 kata-containers-cc 3.2.0.azl2-7 on CBL-Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL-Mariner 2.0
- cbl2 rust 1.72.0-9 on CBL Mariner 2.0
- cbl2 virtiofsd 1.8.0-3 on CBL Mariner 2.0
- cbl2 virtiofsd 1.8.0-3 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 6 updates
6 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 1.72.0-9 |
| — | Security Update | 3.2.0.azl4-1 |
| — | Security Update | 0.194.5-2 |
| — | Security Update | 1.8.0-3 |
| — | Security Update | 32.0-7 |
| — | Security Update | 3.2.0.azl2-7 |
🧭 EchelonGraph on CVE-2024-43806
- EchelonGraph score
- 6.5 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2024-43806, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).