NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

`SegQueue` creates zero value of any typeGHSA-8gj8-hv75-gp94

Fix: crossbeam-rs/crossbeam#458

GHSA-8gj8-hv75-gp94 is a security vulnerability in crossbeam. A fix is available for crossbeam — see the affected versions and patch details below.

Also known asRUSTSEC-2022-0020
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀crossbeam

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iocrossbeamall versions0.7.0cargo update -p crossbeam --precise 0.7.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for crossbeam, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update crossbeam to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8gj8-hv75-gp94 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-8gj8-hv75-gp94 in your dependencies?

Find it across crates.io, including transitive dependencies.

`SegQueue` creates zero value of any type