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 wmi

Dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.40maybe insecure
 futures^0.30.3.31up to date
 log^0.40.4.26up to date
 serde^1.01.0.219up to date
 thiserror^22.0.12up to date
 time^0.30.3.39up to date
 windows^0.590.60.0out of date
 windows-core^0.590.60.1out of date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.101.13.0up to date
 criterion^0.50.5.1up to date
 serde_json^1.01.0.140up to date
 tempdir^0.30.3.7up to date
 tokio ⚠️^1.20.01.44.1maybe insecure

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