CVE-2020-15254High· 8.1▾ Twilightcrossbeam-channel Undefined Behavior before v0.4.4
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 44.6 · likelihood 0.5 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 9.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
2.7%
2.7% → 2.8%
The affected version of this crate's the bounded channel incorrectly assumes that Vec::from_iter has allocated capacity that same as the number of iterator elements. Vec::from_iter does not actually guarantee that and may allocate extra memory. The destructor of the bounded channel reconstructs Vec from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when Vec::from_iter has allocated different sizes with the number of iterator elements.
This has been fixed in crossbeam-channel 0.4.4.
We recommend users to upgrade to 0.4.4.
See https://github.com/crossbeam-rs/crossbeam/pull/533, https://github.com/crossbeam-rs/crossbeam/issues/539, and https://github.com/RustSec/advisory-db/pull/425 for more details.
This advisory is in the public domain.
crossbeam-channel >= 0.4.3, < 0.4.4Upgrade to a patched release:
crossbeam-channel 0.4.4