This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
distill-loader(16 total, 7 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| capnp ⚠️ | ^0.14.0 | 0.21.7 | out of date |
| capnp-rpc | ^0.14.0 | 0.21.0 | out of date |
| crossbeam-channel | ^0.5.0 | 0.5.15 | up to date |
| dashmap | ^4.0.1 | 6.1.0 | out of date |
| distill-core | =0.0.2 | 0.0.3 | out of date |
| distill-schema | =0.0.2 | 0.0.3 | out of date |
| futures-channel | ^0.3 | 0.3.31 | up to date |
| futures-core | ^0.3 | 0.3.31 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| log | ^0.4 | 0.4.28 | up to date |
| memmap | ^0.7 | 0.7.0 | up to date |
| serde | ^1 | 1.0.228 | up to date |
| thread_local ⚠️ | ^1.0 | 1.1.9 | maybe insecure |
| tokio ⚠️ | ^1.0 | 1.48.0 | maybe insecure |
| tokio-util | ^0.6.1 | 0.7.16 | out of date |
| uuid | ^0.8.2 | 1.18.1 | out of date |
thread_local: Data race in `Iter` and `IterMut`In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race
when iterating over a ThreadLocal's values.
Crates using Iter::next, or IterMut::next are affected by this issue.
capnp: out-of-bounds read possible when setting list-of-pointersIf a message consumer expects data of type "list of pointers", and if the consumer performs certain specific actions on such data, then a message producer can cause the consumer to read out-of-bounds memory. This could trigger a process crash in the consumer, or in some cases could allow exfiltration of private in-memory data.
The C++ Cap'n Proto library is also affected by this bug. See the advisory on the main Cap'n Proto repo for a succinct description of the exact circumstances in which the problem can arise.
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);