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 dalybms

Dependencies

(18 total, 2 possibly insecure)

CrateRequiredLatestStatus
 thiserror^22.0.12up to date
 log^0.40.4.27up to date
 serde^11.0.219up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 paho-mqtt^0.13.30.13.3up to date
 serialport^44.7.2up to date
 tokio-serial^55.4.5up to date
 tokio ⚠️^11.47.1maybe insecure
 anyhow^11.0.98up to date
 clap^44.5.42up to date
 clap-verbosity-flag^33.0.3up to date
 clap-num^11.2.0up to date
 humantime^22.2.0up to date
 flexi_logger^0.310.31.2up to date
 chrono ⚠️^0.40.4.41maybe insecure
 rand^0.90.9.2up to date
 serde_json^1.01.0.142up to date
 humantime-serde^11.1.1up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^33.20.0up 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);