GHSA-p7mj-xvxg-grff json
`out_reference::Out::from_raw` should be `unsafe`
published 5y ago modified 3y ago also RUSTSEC-2021-0152
- 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
`Out::from_raw` in affected versions allows writing a value to invalid memory address without requiring `unsafe`.
The soundness issue has been addressed by making `Out::from_raw` an unsafe function.
Patch / fix
- crates.io out-reference 0.2.0
Is GHSA-p7mj-xvxg-grff 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 | out-reference | >=0.1.0, <0.2.0 |
0.2.0 |
References
-
github.com
/RustyYato/out-ref/issues/1
web, report
-
rustsec.org
/advisories/RUSTSEC-2021-0152.html
web, advisory
-
crates.io
/crates/out-reference
package
Sources
- GitHub Advisory GHSA-p7mj-xvxg-grff
- OSV RUSTSEC-2021-0152
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.