RUSTSEC-2020-0072

See a problem?
Please try reporting it to the source first.
Source
https://rustsec.org/advisories/RUSTSEC-2020-0072
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2020-0072.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2020-0072
Aliases
Published
2020-10-31T12:00:00Z
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
GenericMutexGuard allows data races of non-Sync types across threads
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.

This bug is similar to one in std::sync::Mutex.

Database specific 
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / futures-intrusive

Package

Name
futures-intrusive
View open source insights on deps.dev
Purl
pkg:cargo/futures-intrusive

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
0.4.0

Ecosystem specific 

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific 

{
    "cvss": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
    "informational": "unsound",
    "categories": [
        "memory-corruption",
        "thread-safety"
    ]
}