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-daemon(29 total, 16 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-channel | ^1.4 | 2.3.1 | out of date |
| async-lock | ^2.1 | 3.3.0 | out of date |
| bincode | ^1.3.1 | 1.3.3 | up to date |
| capnp ⚠️ | ^0.14.0 | 0.19.5 | out of date |
| capnp-rpc | ^0.14.0 | 0.19.1 | out of date |
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
| distill-core | =0.0.2 | 0.0.3 | out of date |
| distill-downstream-lmdb-rkv | ^0.11.0-windows-fix | N/A | up to date |
| distill-importer | =0.0.2 | 0.0.3 | out of date |
| distill-loader | =0.0.2 | 0.0.3 | out of date |
| distill-schema | =0.0.2 | 0.0.3 | out of date |
| dunce | ^1.0 | 1.0.4 | up to date |
| erased-serde | ^0.3 | 0.4.5 | out of date |
| event-listener | ^2.4.0 | 5.3.0 | out of date |
| fern | ^0.6.0 | 0.6.2 | up to date |
| futures | ^0.3 | 0.3.30 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| notify | ^4.0.15 | 6.1.1 | out of date |
| num_cpus | ^1.10 | 1.16.0 | up to date |
| path-clean | ^0.1 | 1.0.1 | out of date |
| path-slash | ^0.1.1 | 0.2.1 | out of date |
| pin-project | ^1.0 | 1.1.5 | up to date |
| rayon | ^1.3 | 1.10.0 | up to date |
| ron | ^0.6.4 | 0.8.1 | out of date |
| serde | ^1 | 1.0.202 | up to date |
| serde_derive | ^1.0 | 1.0.202 | up to date |
| tokio ⚠️ | ^1.0 | 1.37.0 | maybe insecure |
| tokio-util | ^0.6.1 | 0.7.11 | out of date |
| uuid | ^0.8.2 | 1.8.0 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tempfile | ^3.2.0 | 3.10.1 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
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);