Vulnerability MediumRUSTSEC-2024-0374 · ouch
RUSTSEC-2024-0374: Segmentation fault due to use of uninitialized memory
Short answerA security vulnerability in the ouch crate: Segmentation fault due to use of uninitialized memory. GitHub rates it Medium. Fixed in 0.3.2: update to a fixed version.
| Crate | ouch |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 0.3.2. |
| Fixed in | 0.3.2 |
| Severity | Medium (GitHub rating) |
| Published | 2024-09-22 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-2wq5-g96f-mv3v |
| Affected functions | ouch::archive::zip::convert_zip_date_time |
What to do
- See which version you have:
cargo tree -i ouch(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p ouch. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleouch = "0.3.2") 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
When trying to decompress a file using "ouch", we can reach the function "ouch::archive::zip::convert_zip_date_time". In the function, there is a unsafe function, "transmute". Once the "transmute" function is called to convert the type of "month" object, the address of the object is changed to the uninitialized memory region. After that, when other function tries to dereference "month", segmentation fault occurs.
References
- Package: crates.io/crates/ouch
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0374.html
- Report: github.com/ouch-org/ouch/issues/707
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for ouch
Up next
Same crateouch: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?