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.
rquickjs-core(8 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-lock | ^3 | 3.4.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| dlopen | ^0.1 | 0.1.8 | up to date |
| either | ^1 | 1.13.0 | up to date |
| indexmap | ^2 | 2.6.0 | up to date |
| phf | ^0.11 | 0.11.2 | up to date |
| relative-path | ^1.9 | 1.9.3 | up to date |
| rquickjs-sys | ^0.6.2 | 0.6.2 | up to date |
(4 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| approx | ^0.5 | 0.5.1 | up to date |
| futures | ^0.3 | 0.3.31 | up to date |
| tokio ⚠️ | ^1.0 | 1.41.1 | maybe insecure |
| trybuild | ^1.0.23 | 1.0.101 | 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);