Описание
Data races in ticketed_lock
Affected versions of this crate unconditionally implemented Send for ReadTicket & WriteTicket. 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/WriteTicket). 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/WriteTicket.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2020-36439
- https://github.com/kvark/ticketed_lock/issues/7
- https://github.com/kvark/ticketed_lock/commit/a986a9335d591fa5c826157d1674d47aa525357f
- https://github.com/kvark/ticketed_lock
- https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md
- https://rustsec.org/advisories/RUSTSEC-2020-0119.html
Пакеты
Наименование
ticketed_lock
rust
Затронутые версииВерсия исправления
< 0.3.0
0.3.0
Связанные уязвимости
CVSS3: 8.1
nvd
больше 4 лет назад
An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.