GHSA-6888-wf7j-34jq `SegQueue` creates zero value of any type
Unsound memory initialization in SegQueue can cause null pointer dereferences or memory corruption, potentially leading to crashes or arbitrary code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-6888-wf7j-34jq?
GHSA-6888-wf7j-34jq is a memory corruption vulnerability in crossbeam-queue, published on 10 May 2022.
Official description
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.
Which versions are affected by GHSA-6888-wf7j-34jq?
3 open source packages ship an affected version, including crossbeam-queue.
| Package | Affected | Fixed in |
|---|---|---|
crossbeam-queue crates.io | All versions | 0.2.3 |
crossbeam-queue crates.io | All versions | 0.2.3 |
crossbeam-queue crates.io | From 0.0.0-0 | 0.2.3 |
How do I fix GHSA-6888-wf7j-34jq?
Upgrade crossbeam-queue to 0.2.3 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is GHSA-6888-wf7j-34jq being exploited?
There is no known exploitation of GHSA-6888-wf7j-34jq in the wild and no public exploit code.
Sources
Also known as RUSTSEC-2022-0021.