GHSA-2qv5-7mw5-j3cg json
spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers
published 3y ago modified 2mo ago also RUSTSEC-2023-0031
- 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
`Once::try_call_once` is unsound if invoked more than once concurrently and any call fails to initialise successfully.
Patch / fix
- crates.io spin 0.9.8
Is GHSA-2qv5-7mw5-j3cg 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 | spin | >=0.9.3, <0.9.8 |
0.9.8 |
References
-
github.com
/mvdnes/spin-rs/issues/148
web, report
-
github.com
/mvdnes/spin-rs
package
-
rustsec.org
/advisories/RUSTSEC-2023-0031.html
web, advisory
-
crates.io
/crates/spin
package
Sources
- GitHub Advisory GHSA-2qv5-7mw5-j3cg
- OSV RUSTSEC-2023-0031
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.