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

Crate sled

Dependencies

(12 total, 3 outdated, 1 insecure)

CrateRequiredLatestStatus
 backtrace^0.3.540.3.71up to date
 color-backtrace^0.4.20.6.1out of date
 crc32fast^1.2.11.4.0up to date
 crossbeam-epoch^0.9.00.9.18up to date
 crossbeam-utils^0.8.00.8.19up to date
 fs2^0.4.30.4.3up to date
 fxhash^0.2.10.2.1up to date
 libc^0.2.800.2.153up to date
 log^0.4.110.4.21up to date
 parking_lot^0.11.00.12.2out of date
 rio ⚠️^0.9.40.9.4insecure
 zstd^0.5.30.13.1out of date

Dev dependencies

(8 total, 6 outdated)

CrateRequiredLatestStatus
 byteorder^1.3.41.5.0up to date
 env_logger^0.8.10.11.3out of date
 log^0.4.110.4.21up to date
 quickcheck^0.9.21.0.3out of date
 rand^0.7.30.8.5out of date
 rand_chacha^0.2.20.3.1out of date
 rand_distr^0.3.00.4.3out of date
 zerocopy^0.3.00.7.32out 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.