How severe is GHSA-2jq9-6xx7-3h29?

No CVSS score has been assigned to GHSA-2jq9-6xx7-3h29 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2jq9-6xx7-3h29?

GHSA-2jq9-6xx7-3h29 affects the following packages: temporary (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2jq9-6xx7-3h29?

Update temporary to 0.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jq9-6xx7-3h29 is resolved across your whole dependency graph.

How do I detect GHSA-2jq9-6xx7-3h29 in my crates.io dependencies?

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

How do I mitigate GHSA-2jq9-6xx7-3h29 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-2jq9-6xx7-3h29 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2jq9-6xx7-3h29 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-2jq9-6xx7-3h29 published, and has it been updated?

GHSA-2jq9-6xx7-3h29 was published on August 11, 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.

GHSA-2jq9-6xx7-3h29: temporary

Real-World Exposure

1 pkg affected

🦀temporary

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

Uninitialized memory is used as a RNG seed in temporary. This has been resolved in the 0.6.4 release. The crate is not intended to be used outside of a testing environment. For a general purpose crate to create temporary directories, tempfile is an alternative for this crate.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`temporary`	≥ 0.3.0&&< 0.6.4	0.6.4`cargo update -p temporary --precise 0.6.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for temporary, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update temporary to 0.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jq9-6xx7-3h29 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

Uninitialized memory is used as a RNG seed in temporary. This has been resolved in the 0.6.4 release. The crate is not intended to be used outside of a testing environment. For a general purpose crate to create temporary directories, [`tempfile`](https://crates.io/crates/tempfile) is an alternative for this crate.

O3 Security · Impact-Aware SCA

Is GHSA-2jq9-6xx7-3h29 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

`temporary` makes use of uninitialized memoryGHSA-2jq9-6xx7-3h29