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 tracing-loki

Dependencies

(13 total, 1 possibly insecure)

CrateRequiredLatestStatus
 loki-api^0.1.00.1.3up to date
 reqwest>=0.11.10, <0.13.00.12.12up to date
 serde^1.0.1361.0.219up to date
 serde_json^1.0.791.0.140up to date
 snap^1.0.51.1.1up to date
 tokio ⚠️^1.17.01.44.0maybe insecure
 tokio-stream^0.1.80.1.17up to date
 tracing^0.1.320.1.41up to date
 tracing-core^0.1.230.1.33up to date
 tracing-log>=0.1.2, <0.3.00.2.0up to date
 tracing-serde>=0.1.3, <0.3.00.2.0up to date
 tracing-subscriber^0.3.90.3.19up to date
 url^2.2.22.5.4up to date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.17.01.44.0maybe insecure

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