Advisory

RUSTSEC-2020-0119

Also known as: CVE-2020-36439, GHSA-77m6-x95j-75r5, GHSA-gq4h-f254-7cw9

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>.

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-17 12:00 UTC
Modified
2023-11-08 04:03 UTC

Affected packages and fixes

ticketed_lock

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.3.0 (semver)

Fixed versions

0.3.0

Fix

  • Fixed version 0.3.0
    cargo update -p ticketed_lock --precise 0.3.0

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