Rust advisories / concread
Unsound MediumRUSTSEC-2020-0092 · concread
RUSTSEC-2020-0092: Send/Sync bound needed on V in `impl Send/Sync for ARCache<K, V>`
Short answerconcread has an API that can cause undefined behaviour from safe code: Send/Sync bound needed on V in `impl Send/Sync for ARCache<K, V>`. Fixed in 0.2.6.
| Crate | concread |
|---|---|
| Type | Unsound (thread-safety) |
| Affected versions | Before 0.2.6. |
| Fixed in | 0.2.6 |
| Severity | Medium, CVSS 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-11-13 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35928, GHSA-4xj5-vv9x-63jp |
What to do
- See which version you have:
cargo tree -i concread(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p concread. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleconcread = "0.2.6") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions of this crate unconditionally implemented Send/Sync traits for ARCache<K, V> type.
This allows users to send/access types that do not implement Send/Sync, which can cause a data race.
The flaw was corrected in the 0.2.6 release by adding bounds K: Send + Sync & V: Send + Sync to affected Send/Sync trait implementations.
References
- Package: crates.io/crates/concread
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0092.html
- Report: github.com/kanidm/concread/issues/48
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?