Rust advisories / gfwx
Vulnerability HighRUSTSEC-2020-0104 · gfwx
RUSTSEC-2020-0104: ImageChunkMut needs bounds on its Send and Sync traits
Short answerA security vulnerability in the gfwx crate: ImageChunkMut needs bounds on its Send and Sync traits. High severity (CVSS 7.0). Fixed in 0.3.0: update to a fixed version.
| Crate | gfwx |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.3.0. |
| Fixed in | 0.3.0 |
| Severity | High, CVSS 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-12-08 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36211, GHSA-xp6v-qx65-4pp7 |
What to do
- See which version you have:
cargo tree -i gfwx(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p gfwx. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplegfwx = "0.3.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
In the affected versions of this crate, ImageChunkMut<'_, T> unconditionally implements Send and Sync, allowing to create data races.
This can result in a memory corruption or undefined behavior when non thread-safe types are moved and referenced across thread boundaries.
The flaw was corrected in commit e7fb2f5 by adding T: Send bound to the Send impl and adding T: Sync bound to the Sync impl.
References
- Package: crates.io/crates/gfwx
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0104.html
- Report: github.com/Devolutions/gfwx-rs/issues/7
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?