Search for packages
| purl | pkg:cargo/crossbeam-channel@0.4.3 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-unmm-942j-gkh7
Aliases: CVE-2020-15254 GHSA-v5m7-53cv-f3hx |
crossbeam-channel Undefined Behavior before v0.4.4 ### Impact 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. ### Patches This has been fixed in crossbeam-channel 0.4.4. We recommend users to upgrade to 0.4.4. ### References 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. ### License This advisory is in the public domain. |
Affected by 0 other vulnerabilities. |
|
VCID-w377-ghca-5fff
Aliases: CVE-2020-35904 GHSA-m8h8-v6jh-c762 |
Incorrect buffer size in crossbeam-channel 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. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-br2s-a15r-6ffr | Channel creates zero value of any type Affected versions of this crate called `mem::zeroed()` to create values of a user-supplied type `T`. This is unsound e.g. if `T` is a reference type (which must be non-null). The flaw was corrected by avoiding the use of `mem::zeroed()`, using `MaybeUninit` instead. |
GHSA-9g55-pg62-m8hh
|
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2026-04-02T16:58:05.998680+00:00 | GHSA Importer | Affected by | VCID-unmm-942j-gkh7 | https://github.com/advisories/GHSA-v5m7-53cv-f3hx | 38.1.0 |
| 2026-04-02T16:58:00.654408+00:00 | GHSA Importer | Affected by | VCID-w377-ghca-5fff | https://github.com/advisories/GHSA-m8h8-v6jh-c762 | 38.1.0 |
| 2026-04-01T16:02:37.769197+00:00 | GHSA Importer | Fixing | VCID-br2s-a15r-6ffr | https://github.com/advisories/GHSA-9g55-pg62-m8hh | 38.0.0 |