RUSTSEC-2020-0021
on 2020-05-11: rio allows a use-after-free buffer access when a future is leaked
This crate has no reviews yet. To add a review, set up your cargo-crev.
Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock,
are in the crate's repository. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.
To review the actual code of the crate, it's best to use cargo crev open rio. Alternatively, you can download the tarball of rio v0.9.4 or view the source online.
When a
rio::Completionis leaked, its drop code will not run. The drop code is responsible for waiting until the kernel completes the I/O operation into, or out of, the buffer borrowed byrio::Completion. Leaking the struct will allow one to access and/or drop the buffer, which can lead to a use-after-free, data races or leaking secrets.Upstream is not interested in fixing the issue.
CVE-2020-35876
GHSA-8rc5-mr4f-m243