This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate sled

Dependencies

(15 total, 9 outdated, 1 insecure)

CrateRequiredLatestStatus
 color-backtrace^0.3.00.6.1out of date
 crc32fast^1.2.01.4.0up to date
 crossbeam-epoch^0.8.00.9.18out of date
 crossbeam-utils^0.7.00.8.19out of date
 fail^0.3.00.5.1out of date
 fs2^0.4.30.4.3up to date
 fxhash^0.2.10.2.1up to date
 libc^0.2.650.2.153up to date
 log^0.4.80.4.21up to date
 parking_lot^0.10.00.12.1out of date
 rand^0.7.20.8.5out of date
 rand_chacha^0.2.10.3.1out of date
 rand_distr^0.2.20.4.3out of date
 rio ⚠️^0.9.20.9.4insecure
 zstd^0.5.00.13.1out of date

Dev dependencies

(7 total, 6 outdated)

CrateRequiredLatestStatus
 env_logger^0.7.10.11.3out of date
 fail^0.3.00.5.1out of date
 log^0.4.80.4.21up to date
 quickcheck^0.9.01.0.3out of date
 rand^0.7.20.8.5out of date
 rand_chacha^0.2.10.3.1out of date
 rand_distr^0.2.20.4.3out of date

Security Vulnerabilities

rio: rio allows a use-after-free buffer access when a future is leaked

RUSTSEC-2020-0021

When a rio::Completion is 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 by rio::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.