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.
near-primitives(29 total, 14 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| arbitrary | ^1.2.3 | 1.3.2 | up to date |
| borsh | ^0.10.2 | 1.5.0 | out of date |
| bytesize | ^1.1 | 1.3.0 | up to date |
| cfg-if | ^1 | 1.0.0 | up to date |
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
| derive_more | ^0.99.9 | 0.99.17 | up to date |
| easy-ext | ^0.2 | 1.0.1 | out of date |
| enum-map | ^2.1.0 | 2.7.3 | up to date |
| hex | ^0.4.2 | 0.4.3 | up to date |
| near-crypto | ^0.16.1 | 0.22.0 | out of date |
| near-o11y | ^0.16.1 | 0.22.0 | out of date |
| near-primitives-core | ^0.16.1 | 0.22.0 | out of date |
| near-rpc-error-macro | ^0.16.1 | 0.22.0 | out of date |
| near-vm-errors | ^0.16.1 | 3.1.0 | out of date |
| num-rational | ^0.3.1 | 0.4.2 | out of date |
| once_cell | ^1.13.1 | 1.19.0 | up to date |
| primitive-types | ^0.10 | 0.12.2 | out of date |
| rand | ^0.8.5 | 0.8.5 | up to date |
| reed-solomon-erasure | ^4 | 6.0.0 | out of date |
| serde | ^1.0.136 | 1.0.202 | up to date |
| serde_json | ^1.0.68 | 1.0.117 | up to date |
| serde_yaml | ^0.9 | 0.9.34+deprecated | up to date |
| smart-default | ^0.6 | 0.7.1 | out of date |
| near-stdx | ^0.16.0 | 0.22.0 | out of date |
| strum | ^0.24 | 0.26.2 | out of date |
| thiserror | ^1.0.30 | 1.0.61 | up to date |
| time | ^0.3.9 | 0.3.36 | up to date |
| tokio ⚠️ | ~1.19 | 1.37.0 | out of date |
| tracing | ^0.1.36 | 0.1.40 | up to date |
(3 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_matches | ^1.5.0 | 1.5.0 | up to date |
| bencher | ^0.1.5 | 0.1.5 | up to date |
| insta | ^1.26.0 | 1.39.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);