Rust advisories / max7301
Vulnerability MediumRUSTSEC-2020-0152 · max7301
RUSTSEC-2020-0152: ImmediateIO and TransactionalIO can cause data races
Short answerA security vulnerability in the max7301 crate: ImmediateIO and TransactionalIO can cause data races. Medium severity (CVSS 5.9). Fixed in 0.2.0: update to a fixed version.
| Crate | max7301 |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 0.2.0. |
| Fixed in | 0.2.0 |
| 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-18 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36472, GHSA-rmff-f8w9-c9rm |
What to do
- See which version you have:
cargo tree -i max7301(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p max7301. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplemax7301 = "0.2.0") 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
The ImmediateIO and TransactionalIO types implement Sync for all contained Expander<EI> types regardless of if the Expander itself is safe to use across threads.
As the IO types allow retrieving the Expander, this can lead to non-thread safe types being sent across threads as part of the Expander leading to data races.
References
- Package: crates.io/crates/max7301
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0152.html
- Report: github.com/edarc/max7301/issues/1
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?