GitHub Advisoryadvisory · crates.io
GHSA-fg7r-2g4j-5cgr Race Condition in tokio
HIGH
Official page ↗
- Aliases
- CVE-2021-45710
- Ecosystem
- crates.io
- Packages
- tokio
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-362
- Reviewed
- 2022-01-05
Affected packages
• crates.io tokio: >= 0.1.14, < 1.8.4 → fixed in 1.8.4
• crates.io tokio: >= 1.9.0, < 1.13.1 → fixed in 1.13.1
Description
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.
Related
Alias · CVE (1)
- CVE-2021-45710 An issue was discovered in the tokio crate before 1.8.4, and 1.9.x through 1.13.x before 1.13.1, for Rust. vulnerability
Weakness · CWE (1)
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness