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 llmproxy

Dependencies

(16 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.70.8.6out of date
 hyper^1.6.01.7.0up to date
 hyper-util^0.1.110.1.17up to date
 rand^0.9.10.9.2up to date
 reqwest^0.12.150.12.23up to date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 tokio ⚠️^11.47.1maybe insecure
 tower^0.5.20.5.2up to date
 tower-http^0.50.6.6out of date
 tracing^0.1.410.1.41up to date
 tracing-subscriber^0.3.190.3.20up to date
 clap^44.5.48up to date
 clap-verbosity-flag^3.0.23.0.4up to date
 comfy-table^7.1.17.2.1up to date
 colored^2.1.03.0.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 httptest^0.16.30.16.3up to date
 mime^0.3.170.3.17up to 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);