RUSTSEC-2020-0126

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

Source

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

Import Source

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

JSON Data

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

Aliases

Published

2020-11-15T12:00:00Z

Modified

2023-11-08T04:03:45.337562Z

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

SyncChannel<T> can move 'T: !Send' to other threads

Details

Affected versions of this crate unconditionally implement Send/Sync for SyncChannel<T>. SyncChannel<T> doesn't provide access to &T but merely serves as a channel that consumes and returns owned T.

Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs. Using T = Arc<Cell<_> allows to create data races (which can lead to memory corruption), and using T = MutexGuard<T> allows to unlock a mutex from a thread that didn't lock the mutex.

Database specific

{
    "license": "CC0-1.0"
}

References

Affected packages

crates.io / signal-simple

Package

Name: signal-simple; View open source insights on deps.dev
Purl: pkg:cargo/signal-simple

Affected ranges

Type: SEMVER
Events: Introduced

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