How severe is GHSA-gfg9-x6px-r7gr?

No CVSS score has been assigned to GHSA-gfg9-x6px-r7gr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gfg9-x6px-r7gr?

GHSA-gfg9-x6px-r7gr affects the following packages: plutonium (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-gfg9-x6px-r7gr?

The records we use list no patched version of plutonium for GHSA-gfg9-x6px-r7gr. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-gfg9-x6px-r7gr in my crates.io dependencies?

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

How do I mitigate GHSA-gfg9-x6px-r7gr 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-gfg9-x6px-r7gr actively exploited in the wild?

No public exploit code has been indexed for GHSA-gfg9-x6px-r7gr 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-gfg9-x6px-r7gr published, and has it been updated?

GHSA-gfg9-x6px-r7gr 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

Library exclusively intended to obfuscate codeGHSA-gfg9-x6px-r7gr

GHSA-gfg9-x6px-r7gr is a security vulnerability in plutonium. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2020-0011

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀plutonium

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

This crate allows you to write safe functions with unsafe bodies without the unsafe keyword.

The value this adds is questionable, and hides unsafe usages from naive analysis.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`plutonium`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plutonium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of plutonium for GHSA-gfg9-x6px-r7gr. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

This crate allows you to write safe functions with unsafe bodies without the `unsafe` keyword. The value this adds is questionable, and hides `unsafe` usages from naive analysis.

O3 Security · Impact-Aware SCA

Is GHSA-gfg9-x6px-r7gr in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works