This project contains known security vulnerabilities. Find detailed information at the bottom.
minimp3(4 total, 1 insecure, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| minimp3-sys | ^0.3 | 0.3.2 | up to date |
| slice-deque ⚠️ | ^0.3.0 | 0.3.0 | insecure |
| thiserror | ^1.0.23 | 1.0.68 | up to date |
| tokio ⚠️ | ^1.0 | 1.41.0 | maybe insecure |
(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures | ^0.3.8 | 0.3.31 | up to date |
| tokio ⚠️ | ^1.0 | 1.41.0 | maybe insecure |
slice-deque: SliceDeque::drain_filter can double drop an element if the predicate panicsAffected versions of the crate incremented the current index of the drain filter
iterator before calling the predicate function self.pred.
If the predicate function panics, it is possible for the last element in the iterator to be dropped twice.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);