RUSTSEC-2020-0116

Source
https://rustsec.org/advisories/RUSTSEC-2020-0116
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2020-0116.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2020-0116
Aliases
Published
2020-11-15T12:00:00Z
Modified
2023-11-08T04:03:44.721625Z
Severity
  • 8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
PinSlab<T> and Unordered<T, S> need bounds on their Send/Sync traits
Details

Affected versions of this crate unconditionally implemented Send & Sync for types PinSlab<T> & Unordered&lt;T, S>. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.

This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within PinSlab<T> or Unordered&lt;T, S> and accessed concurrently from multiple threads.

The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound T: Send to Send impls for PinSlab<T> & Unordered&lt;T, S> and adding T: Sync to Sync impls for PinSlab<T> & Unordered&lt;T, S>.

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

Affected packages

crates.io / unicycle

Package

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
0.7.1

Ecosystem specific

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

Database specific

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