*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
In bumpalo prior to 3.11.1, the lifetime of the iterator produced by Vec::into_iter() is not constrained to the lifetime of the Bump that allocated the vector's memory. Using the iterator after the Bump is dropped causes use-after-free accesses.
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
WS-2022-0064
### Vulnerable Library - windows-0.24.0.crate
RUST for windows before 0.32.0 did not require event handlers to have Send bound despite there being no guarantee of them being called on any particular thread, which can potentially lead to data races and undefined behavior
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2024-32650
### Vulnerable Library - rustls-0.20.4.crate
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.
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2023-34411
### Vulnerable Library - xml-rs-0.8.4.crate
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-24713
### Vulnerable Library - regex-1.5.4.crate
An implementation of regular expressions for Rust. This implementation uses
finite automata and guarantees linear time matching on all inputs.
regex is an implementation of regular expressions for the Rust language. The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API. Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes. All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5. All users accepting user-controlled regexes are recommended to upgrade immediately to the latest version of the regex crate. Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, it us not recommend to deny known problematic regexes.
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2018-16875
### Vulnerable Library - webpki-0.22.0.crate
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.
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
WS-2023-0111
### Vulnerable Library - enumflags2-0.7.3.crate
The macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type. Thus, code like this could create an invalid BitFlags, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected. This affects the crate
enumflags2 from 0.7.0 before 0.7.7.
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2020-26235
### Vulnerable Library - chrono-0.4.19.crate
In Rust time crate from version 0.2.7 and before version 0.2.23, unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires the user to set any environment variable in a different thread than the affected functions. The affected functions are time::UtcOffset::local_offset_at, time::UtcOffset::try_local_offset_at, time::UtcOffset::current_local_offset, time::UtcOffset::try_current_local_offset, time::OffsetDateTime::now_local and time::OffsetDateTime::try_now_local. Non-Unix targets are unaffected. This includes Windows and wasm. The issue was introduced in version 0.2.7 and fixed in version 0.2.23.
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
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-0006
### Vulnerable Library - bumpalo-3.9.1.crateA fast bump allocation arena for Rust.
Library home page: https://crates.io/api/v1/crates/bumpalo/3.9.1/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - lettre-0.10.0-rc.4.crate - rustls-0.20.4.crate - webpki-0.22.0.crate - ring-0.16.20.crate - web-sys-0.3.56.crate - wasm-bindgen-0.2.79.crate - wasm-bindgen-macro-0.2.79.crate - wasm-bindgen-macro-support-0.2.79.crate - wasm-bindgen-backend-0.2.79.crate - :x: **bumpalo-3.9.1.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsIn bumpalo prior to 3.11.1, the lifetime of the iterator produced by Vec::into_iter() is not constrained to the lifetime of the Bump that allocated the vector's memory. Using the iterator after the Bump is dropped causes use-after-free accesses.
Publish Date: 2023-01-14
URL: WS-2023-0006
### CVSS 3 Score Details (9.8)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://rustsec.org/advisories/RUSTSEC-2022-0078.html
Release Date: 2023-01-14
Fix Resolution: bumpalo - 3.11.1
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
WS-2022-0064
### Vulnerable Library - windows-0.24.0.crateRust for Windows
Library home page: https://crates.io/api/v1/crates/windows/0.24.0/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - notify-rust-4.5.6.crate - winrt-notification-0.5.1.crate - :x: **windows-0.24.0.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsRUST for windows before 0.32.0 did not require event handlers to have Send bound despite there being no guarantee of them being called on any particular thread, which can potentially lead to data races and undefined behavior
Publish Date: 2022-01-02
URL: WS-2022-0064
### CVSS 3 Score Details (8.4)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://rustsec.org/advisories/RUSTSEC-2022-0008.html
Release Date: 2022-01-02
Fix Resolution: windows - 0.32.0
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2024-32650
### Vulnerable Library - rustls-0.20.4.crateRustls is a modern TLS library written in Rust.
Library home page: https://crates.io/api/v1/crates/rustls/0.20.4/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - lettre-0.10.0-rc.4.crate - :x: **rustls-0.20.4.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsRustls 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.
Publish Date: 2024-04-19
URL: CVE-2024-32650
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/rustls/rustls/security/advisories/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](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2023-34411
### Vulnerable Library - xml-rs-0.8.4.crateAn XML library in pure Rust
Library home page: https://crates.io/api/v1/crates/xml-rs/0.8.4/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - notify-rust-4.5.6.crate - winrt-notification-0.5.1.crate - :x: **xml-rs-0.8.4.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsThe xml-rs crate before 0.8.14 for Rust and Crab allows a denial of service (panic) via an invalid Publish Date: 2023-06-05
URL: CVE-2023-34411
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2023-34411
Release Date: 2023-06-05
Fix Resolution: xml-rs - 0.8.14
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2022-24713
### Vulnerable Library - regex-1.5.4.crateAn implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
Library home page: https://crates.io/api/v1/crates/regex/1.5.4/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - notify-rust-4.5.6.crate - zbus-2.1.1.crate - zbus_macros-2.1.1.crate - :x: **regex-1.5.4.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability Detailsregex is an implementation of regular expressions for the Rust language. The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API. Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes. All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5. All users accepting user-controlled regexes are recommended to upgrade immediately to the latest version of the regex crate. Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, it us not recommend to deny known problematic regexes.
Publish Date: 2022-03-08
URL: CVE-2022-24713
### CVSS 3 Score Details (7.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/rust-lang/regex/security/advisories/GHSA-m5pq-gvj9-9vr8
Release Date: 2022-03-08
Fix Resolution: regex - 1.5.5
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2018-16875
### Vulnerable Library - webpki-0.22.0.crateWeb PKI X.509 Certificate Verification.
Library home page: https://crates.io/api/v1/crates/webpki/0.22.0/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - lettre-0.10.0-rc.4.crate - rustls-0.20.4.crate - :x: **webpki-0.22.0.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsThe 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: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/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](https://www.whitesourcesoftware.com/full_solution_bolt_github)
WS-2023-0111
### Vulnerable Library - enumflags2-0.7.3.crateEnum-based bit flags
Library home page: https://crates.io/api/v1/crates/enumflags2/0.7.3/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - notify-rust-4.5.6.crate - zvariant-3.1.2.crate - :x: **enumflags2-0.7.3.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsThe macro relied on an expression of the form Enum::Variant always being a variant of the enum. However, it may also be an associated integer constant, in which case there's no guarantee that the value of said constant consists only of bits valid for this bitflag type. Thus, code like this could create an invalid BitFlags, which would cause iterating over it to trigger undefined behavior. As the debug formatter internally iterates over the value, it is also affected. This affects the crate
enumflags2 from 0.7.0 before 0.7.7.
### CVSS 3 Score Details (6.5)Publish Date: 2023-04-23
URL: WS-2023-0111
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://rustsec.org/advisories/RUSTSEC-2023-0035.html
Release Date: 2023-04-23
Fix Resolution: enumflags2 - 0.7.7
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2020-26235
### Vulnerable Library - chrono-0.4.19.crateDate and time library for Rust
Library home page: https://crates.io/api/v1/crates/chrono/0.4.19/download
Path to dependency file: /Cargo.toml
Path to vulnerable library: /Cargo.toml
Dependency Hierarchy: - pling-0.2.0.crate (Root Library) - notify-rust-4.5.6.crate - mac-notification-sys-0.3.0.crate - :x: **chrono-0.4.19.crate** (Vulnerable Library)
Found in HEAD commit: 6968cad7c2fc8e0277ed5d75a82a26e462005f5e
Found in base branch: master
### Vulnerability DetailsIn Rust time crate from version 0.2.7 and before version 0.2.23, unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires the user to set any environment variable in a different thread than the affected functions. The affected functions are time::UtcOffset::local_offset_at, time::UtcOffset::try_local_offset_at, time::UtcOffset::current_local_offset, time::UtcOffset::try_current_local_offset, time::OffsetDateTime::now_local and time::OffsetDateTime::try_now_local. Non-Unix targets are unaffected. This includes Windows and wasm. The issue was introduced in version 0.2.7 and fixed in version 0.2.23.
Publish Date: 2020-11-24
URL: CVE-2020-26235
### CVSS 3 Score Details (5.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://rustsec.org/advisories/RUSTSEC-2020-0071.html
Release Date: 2020-11-24
Fix Resolution: chrono - 0.4.20,time - 0.2.23
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)