How severe is GHSA-p6gj-gpc8-f8xw?

No CVSS score has been assigned to GHSA-p6gj-gpc8-f8xw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p6gj-gpc8-f8xw?

GHSA-p6gj-gpc8-f8xw affects the following packages: nanorand (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-p6gj-gpc8-f8xw?

Update nanorand to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p6gj-gpc8-f8xw is resolved across your whole dependency graph.

How do I detect GHSA-p6gj-gpc8-f8xw in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nanorand. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-p6gj-gpc8-f8xw 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-p6gj-gpc8-f8xw?

O3 pinpoints whether GHSA-p6gj-gpc8-f8xw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p6gj-gpc8-f8xw actively exploited in the wild?

No public exploit code has been indexed for GHSA-p6gj-gpc8-f8xw 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.

What is the EPSS score for GHSA-p6gj-gpc8-f8xw?

GHSA-p6gj-gpc8-f8xw has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-p6gj-gpc8-f8xw published, and has it been updated?

GHSA-p6gj-gpc8-f8xw was published on June 17, 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

GHSA-p6gj-gpc8-f8xw

Aliased mutable references from `tls_rand` & `TlsWyRand`

Also known asCVE-2021-45705 GHSA-r57r-j98g-587fRUSTSEC-2021-0114

Published

Jun 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk64th percentile+0.76%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🦀nanorand

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

TlsWyRand's implementation of Deref unconditionally dereferences a raw pointer, and returns multiple mutable references to the same object, which is undefined behavior.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`nanorand`	≥ 0.5.0&&< 0.6.1	0.6.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nanorand. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nanorand to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p6gj-gpc8-f8xw 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 pinpoints whether GHSA-p6gj-gpc8-f8xw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-p6gj-gpc8-f8xw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`TlsWyRand`'s implementation of `Deref` unconditionally dereferences a raw pointer, and returns multiple mutable references to the same object, which is undefined behavior.

O3 Security · Impact-Aware SCA

Is GHSA-p6gj-gpc8-f8xw in your dependencies?

O3 detects GHSA-p6gj-gpc8-f8xw across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works