CVE-2024-43806: rustix's `rustix :fs::Dir` Iterator With The `linux_raw` Vulnerability

MODERATE
Advisory Identifier: GHSA-c827-hfw6-qwvm
CVSS 6.5
CWE-400
Published
Advisory Summary

CVE-2024-43806 is a MODERATE (CVSS 6.5) :fs::dir` iterator with the `linux_raw` vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting rustix's `rustix libraries in the crates.io ecosystem. The issue involves :fs::dir` iterator with the `linux_raw` backend can cause memory explosion. Remediation is available by upgrading affected packages to version 0.35.15, 0.36.16, 0.37.25, 0.38.19.

CVE-2024-43806 at a Glance

CVE Identifier CVE-2024-43806
GHSA Identifier GHSA-c827-hfw6-qwvm
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product rustix's `rustix
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2024-43806

To remediate this vulnerability, upgrade all affected rustix's `rustix dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

rustix fixed: 0.35.15
Upgrade rustix to 0.35.15
rustix fixed: 0.36.16
Upgrade rustix to 0.36.16
rustix fixed: 0.37.25
Upgrade rustix to 0.37.25
rustix fixed: 0.38.19
Upgrade rustix to 0.38.19
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for rustix

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-43806, inspect your project dependencies for rustix's `rustix:

inspect dependencies for rustix

Analyze the terminal output to locate any version of rustix's `rustix in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.35.15), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In rustix's `rustix, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Details #### Discovery The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. See [this post](https://github.com/imsnif/bandwhich/issues/284#issuecomment-1754321993) and the [Discord thread](https://discord.com/channels/273534239310479360/1161137828395237556) for details. #### Diagnosis This issue is caused by the combination of two independent bugs: 1. Stuck iterator - The `rustix::fs::Dir` iterator can fail to halt after encountering an IO error, causing the caller to be stuck in an infinite loop. 2. Memory over-allocation - `Dir::read_more` incorrectly grows the read buffer unconditionally each time it is called, regardless of necessity. Since `<Dir as Iterator>::next` calls `Dir::read`, which in turn calls `Dir::read_more`, this means an IO error encountered during reading a directory can lead to rapid and unbounded growth of memory use. ### PoC ```rust fn main() -> Result<(), Box<dyn std::error::Error>> { // create a directory, get a FD to it, then unlink the directory but keep the FD std::fs::create_dir("tmp_dir")?; let dir_fd = rustix::fs::openat( rustix::fs::CWD, rustix::cstr!("tmp_dir"), rustix::fs::OFlags::RDONLY | rustix::fs::OFlags::CLOEXEC, rustix::fs::Mode::empty(), )?; std::fs::remove_dir("tmp_dir")?; // iterator gets stuck in infinite loop and memory explodes rustix::fs::Dir::read_from(dir_fd)? // the iterator keeps returning `Some(Err(_))`, but never halts by returning `None` // therefore if the implementation ignores the error (or otherwise continues // after seeing the error instead of breaking), the loop will not halt .filter_map(|dirent_maybe_error| dirent_maybe_error.ok()) .for_each(|dirent| { // your happy path println!("{dirent:?}"); }); Ok(()) } ``` ### Impact 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.

CVE-2024-43806 Affected rustix's `rustix Versions

4 component(s)
Fixed Versions:
0.35.150.36.160.37.250.38.19
Product / Package Ecosystem Affected Versions Fixed Version
rustix
crates.io
≥ 0.35.11
< 0.35.15
0.35.15
rustix
crates.io
≥ 0.36.0
< 0.36.16
0.36.16
rustix
crates.io
≥ 0.37.0
< 0.37.25
0.37.25
rustix
crates.io
≥ 0.38.0
< 0.38.19
0.38.19

References

Frequently Asked Questions

What is CVE-2024-43806?
CVE-2024-43806 is a security vulnerability in rustix's `rustix involving :fs::Dir` iterator with the `linux_raw` backend can cause memory explosion under CWE-400: Uncontrolled Resource Consumption.
Which rustix's `rustix versions are affected?
Affected versions include releases prior to 0.35.15, 0.36.16, 0.37.25, 0.38.19 across affected packages: rustix.
What version fixes CVE-2024-43806?
Upgrading to 0.35.15, 0.36.16, 0.37.25, 0.38.19 (or the latest patched release for your respective branch) resolves the vulnerability.
Is rustix affected?
Yes, rustix is affected in releases prior to 0.35.15, 0.36.16, 0.37.25, 0.38.19. Upgrade your dependency to 0.35.15, 0.36.16, 0.37.25, 0.38.19 or later.
What is the CVSS score of CVE-2024-43806?
CVE-2024-43806 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2024-43806?
CVE-2024-43806 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check crates.io dependencies for CVE-2024-43806?
Run the dependency tree command: 'inspect dependencies for rustix'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c827-hfw6-qwvm",
  "modified" : "2024-08-27T14:22:19Z",
  "published" : "2023-10-18T18:27:47Z",
  "aliases" : [ "CVE-2024-43806" ],
  "summary" : "rustix's `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion",
  "details" : "### Summary\n\nWhen 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.\n\n### Details\n\n#### Discovery\n\nThe symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. See [this post](https://github.com/imsnif/bandwhich/issues/284#issuecomment-1754321993) and the [Discord thread](https://discord.com/channels/273534239310479360/1161137828395237556) for details.\n\n#### Diagnosis\n\nThis issue is caused by the combination of two independent bugs:\n\n1. Stuck iterator\n- The `rustix::fs::Dir` iterator can fail to halt after encountering an IO error, causing the caller to be stuck in an infinite loop.\n2. Memory over-allocation\n- `Dir::read_more` incorrectly grows the read buffer unconditionally each time it is called, regardless of necessity.\n\nSince `<Dir as Iterator>::next` calls `Dir::read`, which in turn calls `Dir::read_more`, this means an IO error encountered during reading a directory can lead to rapid and unbounded growth of memory use.\n\n### PoC\n\n```rust\nfn main() -> Result<(), Box<dyn std::error::Error>> {\n    // create a directory, get a FD to it, then unlink the directory but keep the FD\n    std::fs::create_dir(\"tmp_dir\")?;\n    let dir_fd = rustix::fs::openat(\n        rustix::fs::CWD,\n        rustix::cstr!(\"tmp_dir\"),\n        rustix::fs::OFlags::RDONLY | rustix::fs::OFlags::CLOEXEC,\n        rustix::fs::Mode::empty(),\n    )?;\n    std::fs::remove_dir(\"tmp_dir\")?;\n\n    // iterator gets stuck in infinite loop and memory explodes\n    rustix::fs::Dir::read_from(dir_fd)?\n        // the iterator keeps returning `Some(Err(_))`, but never halts by returning `None`\n        // therefore if the implementation ignores the error (or otherwise continues\n        // after seeing the error instead of breaking), the loop will not halt\n        .filter_map(|dirent_maybe_error| dirent_maybe_error.ok())\n        .for_each(|dirent| {\n            // your happy path\n            println!(\"{dirent:?}\");\n        });\n\n    Ok(())\n}\n```\n\n### Impact\n\nIf 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.\n\nAs 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.\n\nAn 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "rustix"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.35.11"
      }, {
        "fixed" : "0.35.15"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "rustix"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.36.0"
      }, {
        "fixed" : "0.36.16"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "rustix"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.37.0"
      }, {
        "fixed" : "0.37.25"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "rustix"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.38.0"
      }, {
        "fixed" : "0.38.19"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-43806"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/imsnif/bandwhich/issues/284"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/imsnif/bandwhich/issues/284#issuecomment-1754321993"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/rustix/commit/31fd98ca723b93cc6101a3e29843ea5cf094e159"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/rustix/commit/87481a97f4364d12d5d6f30cdd025a0fc509b8ec"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/rustix/commit/df3c3a192cf144af0da8a57417fb4addbdc611f6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/rustix/commit/eecece4a84fc58eafdc809cc2cedd374dee876a5"
  }, {
    "type" : "WEB",
    "url" : "https://discord.com/channels/273534239310479360/1161137828395237556"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bytecodealliance/rustix"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-10-18T18:27:47Z",
    "nvd_published_at" : "2024-08-26T19:15:08Z"
  }
}