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
Rustls is a modern TLS library written in Rust. rustls::ConnectionCommon::complete_io could fall into an infinite loop based on network input. When using a blocking rustls server, if a client send a close_notify message immediately after client_hello, the server's complete_io will get in an infinite loop. This vulnerability is fixed in 0.23.5, 0.22.4, and 0.21.11.
Path to vulnerable library: /vdi/host/Cargo.toml,/Cargo.toml
Dependency Hierarchy:
reqwest-0.11.18.crate (Root Library)
h2-0.3.18.crate
tokio-1.28.1.crate
❌ mio-0.8.6.crate (Vulnerable Library)
Found in base branch: master
Vulnerability Details
Mio is a Metal I/O library for Rust. When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free. For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio. The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected. This vulnerability has been fixed in mio v0.8.11. All versions of mio between v0.7.2 and v0.8.10 are vulnerable. Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable. Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
"idna" 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with "idna" 0.5.0 or earlier.
Concretely, "example.org" and "xn--example-.org" become equal after processing by "idna" 0.5.0 or earlier. Also, "example.org.xn--" and "example.org." become equal after processing by "idna" 0.5.0 or earlier.
In applications using "idna" (but not in "idna" itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an "xn--"-masked name that turns into the name of the target when processed by "idna" 0.5.0 or earlier.
Remedy
Upgrade to "idna" 1.0.3 or later, if depending on "idna" directly, or to "url" 2.5.4 or later, if depending on "idna" via "url". (This issue was fixed in "idna" 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
When upgrading, please take a moment to read about "alternative Unicode back ends for "idna"" (https://docs.rs/crate/idna_adapter/latest).
If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an "issue" (servo/rust-url#992) about combining them with "url" 2.5.4 and "idna" 1.0.3.
Additional information
This issue resulted from "idna" 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in "revision 33 of UTS 46" (https://www.unicode.org/reports/tr46/tr46-33.html#Modifications).
Acknowledgements
Thanks to kageshiron for recognizing the security implications of this behavior.
mend-bolt-for-githubbot
changed the title
reqwest-0.11.18.crate: 2 vulnerabilities (highest severity is: 7.5)
reqwest-0.11.18.crate: 3 vulnerabilities (highest severity is: 7.5)
Apr 2, 2024
mend-bolt-for-githubbot
changed the title
reqwest-0.11.18.crate: 3 vulnerabilities (highest severity is: 7.5)
reqwest-0.11.18.crate: 4 vulnerabilities (highest severity is: 7.5)
Apr 22, 2024
mend-bolt-for-githubbot
changed the title
reqwest-0.11.18.crate: 4 vulnerabilities (highest severity is: 7.5)
reqwest-0.11.18.crate: 5 vulnerabilities (highest severity is: 7.5)
Dec 10, 2024
Vulnerable Library - reqwest-0.11.18.crate
Path to dependency file: /Cargo.toml
Path to vulnerable library: /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
CVE-2024-32650
Vulnerable Library - rustls-0.21.2.crate
Rustls is a modern TLS library written in Rust.
Library home page: https://crates.io/api/v1/crates/rustls/0.21.2/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
Rustls is a modern TLS library written in Rust.
rustls::ConnectionCommon::complete_io
could fall into an infinite loop based on network input. When using a blocking rustls server, if a client send aclose_notify
message immediately afterclient_hello
, the server'scomplete_io
will get in an infinite loop. This vulnerability is fixed in 0.23.5, 0.22.4, and 0.21.11.Publish Date: 2024-04-19
URL: CVE-2024-32650
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-6g7w-8wpp-frhj
Release Date: 2024-04-19
Fix Resolution: rustls - 0.21.11,0.22.4,0.23.5
Step up your Open Source Security Game with Mend here
CVE-2024-27308
Vulnerable Library - mio-0.8.6.crate
Lightweight non-blocking I/O.
Library home page: https://crates.io/api/v1/crates/mio/0.8.6/download
Path to dependency file: /vdi/host/Cargo.toml
Path to vulnerable library: /vdi/host/Cargo.toml,/Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
Mio is a Metal I/O library for Rust. When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free. For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio. The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected. This vulnerability has been fixed in mio v0.8.11. All versions of mio between v0.7.2 and v0.8.10 are vulnerable. Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable. Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.
Publish Date: 2024-03-06
URL: CVE-2024-27308
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-r8w9-5wcg-vfj7
Release Date: 2024-03-06
Fix Resolution: mio - 0.8.11
Step up your Open Source Security Game with Mend here
CVE-2018-16875
Vulnerable Library - rustls-webpki-0.100.1.crate
Web PKI X.509 Certificate Verification.
Library home page: https://crates.io/api/v1/crates/rustls-webpki/0.100.1/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected.
Publish Date: 2018-12-14
URL: CVE-2018-16875
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-fh2r-99q2-6mmg
Release Date: 2018-12-14
Fix Resolution: golang 1.10.6,golang 1.11.3, webpki - 0.22.2, rustls-webpki - 0.100.2,0.101.4
Step up your Open Source Security Game with Mend here
WS-2023-0305
Vulnerable Library - rustls-webpki-0.100.1.crate
Web PKI X.509 Certificate Verification.
Library home page: https://crates.io/api/v1/crates/rustls-webpki/0.100.1/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
rustls-webpki: CPU denial of service in certificate path building
Publish Date: 2024-11-03
URL: WS-2023-0305
CVSS 3 Score Details (5.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-fh2r-99q2-6mmg
Release Date: 2023-08-22
Fix Resolution: rustls-webpki - 0.100.2,0.101.4
Step up your Open Source Security Game with Mend here
CVE-2024-12224
Vulnerable Library - idna-0.3.0.crate
IDNA (Internationalizing Domain Names in Applications) and Punycode.
Library home page: https://crates.io/api/v1/crates/idna/0.3.0/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy:
Found in base branch: master
Vulnerability Details
"idna" 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with "idna" 0.5.0 or earlier.
Concretely, "example.org" and "xn--example-.org" become equal after processing by "idna" 0.5.0 or earlier. Also, "example.org.xn--" and "example.org." become equal after processing by "idna" 0.5.0 or earlier.
In applications using "idna" (but not in "idna" itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an "xn--"-masked name that turns into the name of the target when processed by "idna" 0.5.0 or earlier.
Remedy
Upgrade to "idna" 1.0.3 or later, if depending on "idna" directly, or to "url" 2.5.4 or later, if depending on "idna" via "url". (This issue was fixed in "idna" 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
When upgrading, please take a moment to read about "alternative Unicode back ends for "idna"" (https://docs.rs/crate/idna_adapter/latest).
If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an "issue" (servo/rust-url#992) about combining them with "url" 2.5.4 and "idna" 1.0.3.
Additional information
This issue resulted from "idna" 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in "revision 33 of UTS 46" (https://www.unicode.org/reports/tr46/tr46-33.html#Modifications).
Acknowledgements
Thanks to kageshiron for recognizing the security implications of this behavior.
Publish Date: 2024-12-16
URL: CVE-2024-12224
CVSS 3 Score Details (4.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-h97m-ww89-6jmq
Release Date: 2024-12-09
Fix Resolution: idna - 1.0.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: