How severe is GHSA-9g55-pg62-m8hh?

No CVSS score has been assigned to GHSA-9g55-pg62-m8hh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9g55-pg62-m8hh?

GHSA-9g55-pg62-m8hh affects the following packages: crossbeam-channel (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9g55-pg62-m8hh?

Update crossbeam-channel to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g55-pg62-m8hh is resolved across your whole dependency graph.

How do I detect GHSA-9g55-pg62-m8hh in my crates.io dependencies?

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

How do I mitigate GHSA-9g55-pg62-m8hh if there is no patch (or I can't update yet)?

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.

Is GHSA-9g55-pg62-m8hh actively exploited in the wild?

No public exploit code has been indexed for GHSA-9g55-pg62-m8hh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9g55-pg62-m8hh published, and has it been updated?

GHSA-9g55-pg62-m8hh was published on June 16, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Channel creates zero value of any typeGHSA-9g55-pg62-m8hh

Fix: crossbeam-rs/crossbeam#458

GHSA-9g55-pg62-m8hh is a security vulnerability in crossbeam-channel. A fix is available for crossbeam-channel — see the affected versions and patch details below.

Also known asRUSTSEC-2022-0019

Published

Jun 16, 2022

Updated

Nov 8, 2023

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-channel

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

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`crossbeam-channel`	all versions	0.4.3`cargo update -p crossbeam-channel --precise 0.4.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for crossbeam-channel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update crossbeam-channel to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g55-pg62-m8hh is resolved across your whole dependency graph.
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-9g55-pg62-m8hh in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works