Rust advisories / kekbit
Vulnerability HighRUSTSEC-2020-0129 · kekbit
RUSTSEC-2020-0129: ShmWriter allows sending non-Send type across threads
Short answerA security vulnerability in the kekbit crate: ShmWriter allows sending non-Send type across threads. High severity (CVSS 8.1). Fixed in 0.3.4: update to a fixed version.
| Crate | kekbit |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.3.4. |
| Fixed in | 0.3.4 |
| Severity | High, CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-12-18 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36449, GHSA-g83m-67wh-whpw |
What to do
- See which version you have:
cargo tree -i kekbit(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p kekbit. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplekekbit = "0.3.4") 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 implement Send for ShmWriter<H> without requiring H: Send. This allows users to send H: !Send to other threads, which can potentially lead to data races and undefined behavior.
References
- Package: crates.io/crates/kekbit
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0129.html
- Report: github.com/motoras/kekbit/issues/34
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?