mend-bolt-for-github[bot]
commented
2 years ago :heavy_check_mark: This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.
WS-2021-0424 - Medium Severity Vulnerability
tokio-0.2.11.crate
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Library home page: https://crates.io/api/v1/crates/tokio/0.2.11/download
Dependency Hierarchy: - :x: **tokio-0.2.11.crate** (Vulnerable Library)
tokio-0.2.21.crate
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Library home page: https://crates.io/api/v1/crates/tokio/0.2.21/download
Dependency Hierarchy: - :x: **tokio-0.2.21.crate** (Vulnerable Library)
tokio-1.0.1.crate
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Library home page: https://crates.io/api/v1/crates/tokio/1.0.1/download
Dependency Hierarchy: - :x: **tokio-1.0.1.crate** (Vulnerable Library)
tokio-0.2.13.crate
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Library home page: https://crates.io/api/v1/crates/tokio/0.2.13/download
Dependency Hierarchy: - :x: **tokio-0.2.13.crate** (Vulnerable Library)
tokio-0.2.9.crate
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Library home page: https://crates.io/api/v1/crates/tokio/0.2.9/download
Dependency Hierarchy: - :x: **tokio-0.2.9.crate** (Vulnerable Library)
Found in base branch: master
The crate 'tokio' has a data race when sending and receiving after closing a oneshot channel. Version before 0.1.15 are not affected. Fixed in v1.8.4 and v.1.13.1 If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv. When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption. Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.
Publish Date: 2021-11-16
URL: WS-2021-0424
Base Score Metrics: - Exploitability Metrics: - Attack Vector: N/A - Attack Complexity: N/A - Privileges Required: N/A - User Interaction: N/A - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://rustsec.org/advisories/RUSTSEC-2021-0124.html
Release Date: 2021-11-16
Fix Resolution: tokio - 1.8.4,1.13.1
Step up your Open Source Security Game with WhiteSource here