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, 18 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-channel | ^1.4 | 2.5.0 | out of date |
| async-lock | ^2.1 | 3.4.2 | out of date |
| bincode | ^1.3.1 | 3.0.0 | out of date |
| capnp ⚠️ | ^0.14.0 | 0.25.3 | out of date |
| capnp-rpc | ^0.14.0 | 0.25.0 | out of date |
| chrono ⚠️ | ^0.4.19 | 0.4.44 | 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.5 | up to date |
| erased-serde | ^0.3 | 0.4.10 | out of date |
| event-listener | ^2.4.0 | 5.4.1 | out of date |
| fern | ^0.6.0 | 0.7.1 | out of date |
| futures | ^0.3 | 0.3.32 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| notify | ^4.0.15 | 8.2.0 | out of date |
| num_cpus | ^1.10 | 1.17.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.11 | up to date |
| rayon | ^1.3 | 1.11.0 | up to date |
| ron | ^0.6.4 | 0.12.1 | out of date |
| serde | ^1 | 1.0.228 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| tokio ⚠️ | ^1.0 | 1.50.0 | maybe insecure |
| tokio-util | ^0.6.1 | 0.7.18 | out of date |
| uuid | ^0.8.2 | 1.23.0 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tempfile | ^3.2.0 | 3.27.0 | 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.
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);
capnp: Unsound APIs of public `constant::Reader` and `StructSchema`The safe API functions constant::Reader::get and StructSchema::new rely on PointerReader::get_root_unchecked, which can cause undefined behavior (UB) by constructing arbitrary words or schemas.
Reader::getpub fn get(&self) -> Result<<T as Owned>::Reader<'static>> {
// ...
// UNSAFE: access `words` without validation
}
StructSchema::newpub fn new(builder: RawBrandedStructSchema) -> StructSchema {
// ...
// UNSAFE: access encoded nodes without validation
}
This vulnerability allows safe Rust code to trigger UB, which violates Rust's safety guarantees.
The issue is resolved in version 0.24.0 by making constructor functions unsafe and mark the fields of struct as visible only in the crate.