RUSTSEC-2020-0113
Dashboard / Vulnerabilities / RUSTSEC-2020-0113
RUSTSEC-2020-0113
Published: 31 Oct 2020Last Modified: 8 Nov 2023
Aliases:
Summary: AtomicOption should have Send + Sync bound on its type argument.
Details: In the affected versions of this crate, `AtomicOption<T>` unconditionally implements `Sync`. This allows programmers to move non-Sync types across thread boundaries (e.g. `Rc<T>`, `Arc<Cell<T>>`), which can lead to data races and undefined behavior. It is also possible to send non-Send types like `std::sync::MutexGuard` to other threads, which can lead to undefined behavior.
References: https://crates.io/crates/atomic-option, https://rustsec.org/advisories/RUSTSEC-2020-0113.html, https://github.com/reem/rust-atomic-option/issues/4
Affected packages
Package
Name: atomic-option
Purl: pkg:cargo/atomic-option
Affected ranges
Type: SEMVER
Events:
Introduced- 0.0.0-0
Fixed -None
Affected versions
Common Vulnerability Scoring System
Attack Vector
Network
Adjacent
Local
Physical
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
