CVE-2020-15254

Undefined Behavior in bounded Crossbeam channel

CVSS 8.1 HIGHEPSS 2.7%CWE-119

Vexday Risk Score

21Low

SSVC decision (CISA)

Track

No exploitation signal → monitor

CVSS 8.1EPSS 2.7%KEV nãoPoC —Nuclei —Metasploit —Patch —

Lifecycle

16 Oct 2020Published on NVD

Recommendation: Monitor — no exploitation signal at the moment.

Crossbeam is a set of tools for concurrent programming. In crossbeam-channel before version 0.4.4, 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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

crossbeam-rs · crossbeam

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

https://github.com/crossbeam-rs/crossbeam/issues/539 https://github.com/crossbeam-rs/crossbeam/pull/533 https://github.com/crossbeam-rs/crossbeam/security/advisories/GHSA-v5m7-53cv-f3hx https://github.com/RustSec/advisory-db/pull/425