GHSA-6888-wf7j-34jq json
`SegQueue` creates zero value of any type
published 4y ago modified 3y ago also RUSTSEC-2022-0021
- 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
Is GHSA-6888-wf7j-34jq 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | crossbeam-queue | <0.2.3 >=0.0.0-0, <0.2.3 |
0.2.3 |
References
Sources
- GitHub Advisory GHSA-6888-wf7j-34jq
- OSV RUSTSEC-2022-0021
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.