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 mdblog

Dependencies

(23 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.19up to date
 clap^44.5.40up to date
 config^0.140.15.11out of date
 derive_more^12.0.1out of date
 pulldown-cmark^0.110.13.0out of date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 toml^0.80.8.23up to date
 tera^11.20.0up to date
 walkdir^2.32.5.0up to date
 tempfile^33.20.0up to date
 open^55.3.2up to date
 notify^68.1.0out of date
 notify-debouncer-mini^0.40.6.0out of date
 glob^0.30.3.2up to date
 shellexpand^33.1.1up to date
 time^0.30.3.41up to date
 mime_guess^2.0.52.0.5up to date
 axum^0.70.8.4out of date
 tokio ⚠️^11.46.1maybe insecure
 tower-http^0.50.6.6out of date

Security Vulnerabilities

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