How severe is GHSA-ghc8-5cgm-5rpf?

No CVSS score has been assigned to GHSA-ghc8-5cgm-5rpf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ghc8-5cgm-5rpf?

GHSA-ghc8-5cgm-5rpf affects the following packages: inventory (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-ghc8-5cgm-5rpf?

Update inventory to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghc8-5cgm-5rpf is resolved across your whole dependency graph.

How do I detect GHSA-ghc8-5cgm-5rpf in my crates.io dependencies?

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

How do I mitigate GHSA-ghc8-5cgm-5rpf 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.

How does O3 Security protect against GHSA-ghc8-5cgm-5rpf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ghc8-5cgm-5rpf can be triaged on real exposure rather than presence alone.

Is GHSA-ghc8-5cgm-5rpf actively exploited in the wild?

No public exploit code has been indexed for GHSA-ghc8-5cgm-5rpf 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-ghc8-5cgm-5rpf published, and has it been updated?

GHSA-ghc8-5cgm-5rpf was published on September 11, 2023 and was last updated on February 10, 2024. 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

GHSA-ghc8-5cgm-5rpf — inventory

Fix: dtolnay/inventory#43

GHSA-ghc8-5cgm-5rpf is a security vulnerability in inventory. A fix is available for inventory — see the affected versions and patch details below.

Inventory fails to prohibit standard library access prior to initialization of Rust standard library runtime

Also known asRUSTSEC-2023-0057

Published

Sep 11, 2023

Updated

Feb 10, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 10, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀inventory

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 allow arbitrary caller-provided code to execute before the lifetime of main.

If the caller-provided code accesses particular pieces of the standard library that require an initialized Rust runtime, such as std::io or std::thread, these may not behave as documented. Panics are likely; UB is possible.

The flaw was corrected by enforcing that only code written within the inventory crate, which is guaranteed not to access runtime-dependent parts of the standard library, runs before main. Caller-provided code is restricted to running at compile time.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`inventory`	all versions	0.2.0`cargo update -p inventory --precise 0.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for inventory, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update inventory to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghc8-5cgm-5rpf 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ghc8-5cgm-5rpf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-ghc8-5cgm-5rpf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions allow arbitrary caller-provided code to execute before the lifetime of `main`. If the caller-provided code accesses particular pieces of the standard library that require an initialized Rust runtime, such as `std::io` or `std::thread`, these may not behave as documented. Panics are likely; UB is possible. The flaw was corrected by enforcing that only code written within the `inventory` crate, which is guaranteed not to access runtime-dependent parts of the standard library, runs before `main`. Caller-provided code is restricted to running at compile time.

O3 Security · Impact-Aware SCA

Is GHSA-ghc8-5cgm-5rpf in your dependencies?

O3 Security finds GHSA-ghc8-5cgm-5rpf across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works