You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
WS-2023-0366
Vulnerable Library - rustix-0.36.11.crate
Safe Rust bindings to POSIX/Unix/Linux/Winsock2-like syscalls
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 imsnif/bandwhich#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.
mend-bolt-for-githubbot
changed the title
clap-4.1.11.crate: 1 vulnerabilities (highest severity is: 5.5)
clap-4.1.11.crate: 1 vulnerabilities (highest severity is: 6.5)
Mar 14, 2024
mend-bolt-for-githubbot
changed the title
clap-4.1.11.crate: 1 vulnerabilities (highest severity is: 6.5)
clap-4.1.11.crate: 2 vulnerabilities (highest severity is: 6.5)
Aug 27, 2024
Vulnerable Library - clap-4.1.11.crate
Path to dependency file: /vdi/host/Cargo.toml
Path to vulnerable library: /vdi/host/Cargo.toml
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
WS-2023-0366
Vulnerable Library - rustix-0.36.11.crate
Safe Rust bindings to POSIX/Unix/Linux/Winsock2-like syscalls
Library home page: https://crates.io/api/v1/crates/rustix/0.36.11/download
Path to dependency file: /vdi/host/Cargo.toml
Path to vulnerable library: /vdi/host/Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
rustix's
rustix::fs::Dir
iterator with thelinux_raw
backend can cause memory explosionPublish Date: 2023-10-18
URL: WS-2023-0366
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-c827-hfw6-qwvm
Release Date: 2023-10-18
Fix Resolution: rustix - 0.35.15,0.36.16,0.37.25,0.38.19
Step up your Open Source Security Game with Mend here
CVE-2024-43806
Vulnerable Library - rustix-0.36.11.crate
Safe Rust bindings to POSIX/Unix/Linux/Winsock2-like syscalls
Library home page: https://crates.io/api/v1/crates/rustix/0.36.11/download
Path to dependency file: /vdi/host/Cargo.toml
Path to vulnerable library: /vdi/host/Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using
rustix::fs::Dir
using thelinux_raw
backend, it's possible for the iterator to "get stuck" when an IO error is encountered. Combined with a memory over-allocation issue inrustix::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 imsnif/bandwhich#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 theDir
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 usingrustix::fs::Dir
directly or indirectly (e.g. with theprocfs
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.Publish Date: 2024-08-26
URL: CVE-2024-43806
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-c827-hfw6-qwvm
Release Date: 2024-08-26
Fix Resolution: rustix - 0.35.15,0.36.16,0.37.25,0.38.19
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: