Advisory

RUSTSEC-2020-0126

Also known as: CVE-2020-36446, GHSA-36cg-4jff-5863, GHSA-8892-84wf-cg8f

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.

Severity

High Basis: CVSS v3 score 8.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Dates

Published
2020-11-15 12:00 UTC
Modified
2023-11-08 04:03 UTC

Affected packages and fixes

signal-simple

crates.io · All systems

Affected

  • introduced 0.0.0-0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences