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.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
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