Undefined Behavior in bounded Crossbeam channel
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| crossbeam-rs | crossbeam | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-1883 | 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. |
Github GHSA |
GHSA-v5m7-53cv-f3hx | crossbeam-channel Undefined Behavior before v0.4.4 |
Ubuntu USN |
USN-4599-1 | Firefox vulnerabilities |
Ubuntu USN |
USN-4599-2 | Firefox vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.7% (2.701% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.