GHSA-2jq9-6xx7-3h29 json
`temporary` makes use of uninitialized memory
published 8y ago modified 3y ago also RUSTSEC-2018-0022
- 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
Uninitialized memory is used as a RNG seed in temporary. This has been resolved in the 0.6.4 release. The crate is not intended to be used outside of a testing environment. For a general purpose crate to create temporary directories, [`tempfile`](https://crates.io/crates/tempfile) is an alternative for this crate.
Patch / fix
- crates.io temporary 0.6.4
Is GHSA-2jq9-6xx7-3h29 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 | temporary | >=0.3.0, <0.6.4 |
0.6.4 |
References
-
github.com
/stainless-steel/temporary/issues/2
web, report
-
github.com
/stainless-steel/temporary
package
-
rustsec.org
/advisories/RUSTSEC-2018-0022.html
web, advisory
-
crates.io
/crates/temporary
package
Sources
- GitHub Advisory GHSA-2jq9-6xx7-3h29
- OSV RUSTSEC-2018-0022
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.