GitHub Advisoryadvisory · crates.io

GHSA-4hjg-cx88-g9f9 Data races in futures-intrusive

MEDIUM Published 2021-08-25 Modified 2023-06-13 Official page ↗
Aliases
CVE-2020-35915
Ecosystem
crates.io
Packages
futures-intrusive
Severity
Moderate
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-362
Reviewed
2021-08-19

Affected packages

• crates.io futures-intrusive: < 0.4.0 → fixed in 0.4.0

Description

GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.

Related

Alias · CVE (1)

  • CVE-2020-35915 An issue was discovered in the futures-intrusive crate before 0.4.0 for Rust. vulnerability

Weakness · CWE (1)

  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness

References