GHSA-9hpw-r23r-xgm5 json
Data race in `Iter` and `IterMut`
published 4y ago modified 3y ago also RUSTSEC-2022-0006
- 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
In the affected version of this crate, `{Iter, IterMut}::next` used a weaker memory ordering when loading values than what was required, exposing a potential data race when iterating over a `ThreadLocal`'s values.
Crates using `Iter::next`, or `IterMut::next` are affected by this issue.
Patch / fix
- crates.io thread_local 1.1.4
Is GHSA-9hpw-r23r-xgm5 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 | thread_local | <1.1.4 >=0.0.0-0, <1.1.4 |
1.1.4 |
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
github.com
/Amanieu/thread_local-rs/issues/33
web, report
-
github.com
/Amanieu/thread_local-rs
package
-
rustsec.org
/advisories/RUSTSEC-2022-0006.html
web, advisory
-
crates.io
/crates/thread_local
package
Sources
- GitHub Advisory GHSA-9hpw-r23r-xgm5
- OSV RUSTSEC-2022-0006
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.