GHSA-gfg9-x6px-r7gr json
Library exclusively intended to obfuscate code.
published 6y ago modified 3y ago also RUSTSEC-2020-0011
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Is GHSA-gfg9-x6px-r7gr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | plutonium | <=0.5.2 >=0.0.0-0 |
no fix listed |
References
-
github.com
/mxxo/plutonium
package
-
rustsec.org
/advisories/RUSTSEC-2020-0011.html
web, advisory
-
crates.io
/crates/plutonium
package
-
docs.rs
/plutonium
web
Sources
- GitHub Advisory GHSA-gfg9-x6px-r7gr
- OSV RUSTSEC-2020-0011
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.