RUSTSEC-2020-0119

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2020-0119

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2020-0119.json

JSON Data

https://api.osv.dev/v1/vulns/RUSTSEC-2020-0119

Aliases

Published

2020-11-17T12:00:00Z

Modified

2023-11-08T04:03:44.903828Z

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

ReadTicket and WriteTicket should only be sendable when T is Send

Details

Affected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads.

This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior.

The flaw was corrected in commit a986a93 by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / ticketed_lock

Package

Name: ticketed_lock; View open source insights on deps.dev
Purl: pkg:cargo/ticketed_lock

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Fixed

0.3.0

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"
    ]
}