GHSA-4hjg-cx88-g9f9
Suggest an improvement- Source
- https://github.com/advisories/GHSA-4hjg-cx88-g9f9
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/08/GHSA-4hjg-cx88-g9f9/GHSA-4hjg-cx88-g9f9.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-4hjg-cx88-g9f9
- Aliases
-
- CVE-2020-35915
- RUSTSEC-2020-0072
- Published
- 2021-08-25T20:49:58Z
- Modified
- 2023-11-08T04:03:39.161436Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- Data races in futures-intrusive
- Details
-
GenericMutexGuard<T> 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.
- Database specific
{ "nvd_published_at": null, "cwe_ids": [ "CWE-362" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2021-08-19T20:49:04Z" }- References
Affected packages
crates.io / futures-intrusive
Package
- Name
- futures-intrusive
- View open source insights on deps.dev
- Purl
- pkg:cargo/futures-intrusive