Skip to content
Fencer Intel
high —

GHSA-9g55-pg62-m8hh json

Channel creates zero value of any type

published 4y ago modified 3y ago also RUSTSEC-2022-0019

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io crossbeam-channel 0.4.3

Is GHSA-9g55-pg62-m8hh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io crossbeam-channel
<0.4.3
>=0.0.0-0, <0.4.3
0.4.3

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.