GHSA-mpg5-fvwp-42m2 json
Unsoundness in `dashmap` references
published 4y ago modified 3y ago also RUSTSEC-2022-0002
- 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
Reference returned by some methods of `Ref` (and similar types) may outlive the `Ref` and escape the lock. This causes undefined behavior and may result in a segfault.
More information in [`dashmap#167`](https://github.com/xacrimon/dashmap/issues/167) issue.
Patch / fix
- crates.io dashmap 5.1.0
Is GHSA-mpg5-fvwp-42m2 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 | dashmap | >=5.0.0, <5.1.0 |
5.1.0 |
References
-
github.com
/xacrimon/dashmap/issues/167
web, report
-
github.com
/xacrimon/dashmap
package
-
rustsec.org
/advisories/RUSTSEC-2022-0002.html
web, advisory
-
crates.io
/crates/dashmap
package
Sources
- GitHub Advisory GHSA-mpg5-fvwp-42m2
- OSV RUSTSEC-2022-0002
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.