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.

Crate near-network-primitives

Dependencies

(12 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 actix=0.11.0-beta.20.13.5out of date
 actix_derive=0.6.0-beta.10.6.2out of date
 anyhow^1.0.511.0.98up to date
 borsh^0.91.5.7out of date
 chrono ⚠️^0.4.40.4.41maybe insecure
 deepsize^0.2.00.2.0up to date
 near-crypto^0.12.00.30.3out of date
 near-primitives^0.12.00.30.3out of date
 serde^11.0.219up to date
 strum^0.200.27.1out of date
 tokio ⚠️^1.11.46.1maybe insecure
 tracing^0.1.130.1.41up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);