Rust advisories / eventio
Vulnerability MediumRUSTSEC-2020-0108 · eventio
RUSTSEC-2020-0108: Soundness issue: Input<R> can be misused to create data race to an object
Short answerA security vulnerability in the eventio crate: Soundness issue: Input<R> can be misused to create data race to an object. Medium severity (CVSS 5.9). Fixed in 0.5.1: update to a fixed version.
| Crate | eventio |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.5.1. |
| Fixed in | 0.5.1 |
| Severity | Medium, CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-12-20 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36216, GHSA-69vj-xx27-g45w |
What to do
- See which version you have:
cargo tree -i eventio(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p eventio. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleeventio = "0.5.1") 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
Input<R> implements Send without requiring R: Send.
Affected versions of this crate allows users to send non-Send types to other threads, which can lead to undefined behavior such as data race and memory corruption.
The flaw was corrected in version 0.5.1 by adding R: Send bound to the Send impl of Input<R>.
References
- Package: crates.io/crates/eventio
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0108.html
- Report: github.com/petabi/eventio/issues/33
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?