# 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.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2022
- **Also known as:** RUSTSEC-2022-0021

## 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 | Ecosystem | 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.

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6888-wf7j-34jq and fix it if it is affected.

What it is: GHSA-6888-wf7j-34jq is a memory corruption vulnerability in crossbeam-queue, published on 10 May 2022. 
Exploitation: There is no known exploitation of GHSA-6888-wf7j-34jq in the wild and no public exploit code.

Affected packages and fixed versions:
- crossbeam-queue (crates.io): affected all versions; fixed in 0.2.3
- crossbeam-queue (crates.io): affected all versions; fixed in 0.2.3
- crossbeam-queue (crates.io): affected from 0.0.0-0; fixed in 0.2.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-6888-wf7j-34jq/ (Markdown: https://insights.sbomify.com/GHSA-6888-wf7j-34jq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6888-wf7j-34jq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6888-wf7j-34jq/
Summaries are generated and may contain mistakes; the official description above is the record.