# GHSA-gfg9-x6px-r7gr: Library exclusively intended to obfuscate code.

> This Rust crate bypasses the unsafe keyword requirement, hiding unsafe code from static analysis and potentially masking memory safety violations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2020
- **Also known as:** RUSTSEC-2020-0011

## What is GHSA-gfg9-x6px-r7gr?

GHSA-gfg9-x6px-r7gr is a vulnerability in plutonium, published on 23 Apr 2020. 

### Official 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.

## Which versions are affected by GHSA-gfg9-x6px-r7gr?

3 open source packages ship an affected version, including plutonium.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `plutonium` | crates.io | All versions to 0.5.2 | None |
| `plutonium` | crates.io | All versions to 0.5.2 | None |
| `plutonium` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for GHSA-gfg9-x6px-r7gr yet. Limit exposure of the affected software until one is available.

## Is GHSA-gfg9-x6px-r7gr being exploited?

There is no known exploitation of GHSA-gfg9-x6px-r7gr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-gfg9-x6px-r7gr and fix it if it is affected.

What it is: GHSA-gfg9-x6px-r7gr is a vulnerability in plutonium, published on 23 Apr 2020. 
Exploitation: There is no known exploitation of GHSA-gfg9-x6px-r7gr in the wild and no public exploit code.

Affected packages and fixed versions:
- plutonium (crates.io): affected all versions up to 0.5.2; no fix listed
- plutonium (crates.io): affected all versions up to 0.5.2; no fix listed
- plutonium (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-gfg9-x6px-r7gr/ (Markdown: https://insights.sbomify.com/GHSA-gfg9-x6px-r7gr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-gfg9-x6px-r7gr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-gfg9-x6px-r7gr/
Summaries are generated and may contain mistakes; the official description above is the record.