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 brk_rmcp

Dependencies

(27 total, 1 possibly insecure)

CrateRequiredLatestStatus
 axum^0.80.8.4up to date
 base64^0.220.22.1up to date
 bytes^11.10.1up to date
 chrono^0.4.380.4.41up to date
 futures^0.30.3.31up to date
 http^11.3.1up to date
 http-body^11.0.1up to date
 http-body-util^0.10.1.3up to date
 oauth2^5.05.0.0up to date
 paste^11.0.15up to date
 pin-project-lite^0.20.2.16up to date
 process-wrap^8.28.2.1up to date
 rand^0.90.9.1up to date
 reqwest^0.120.12.20up to date
 brk_rmcp-macros^0.1.80.1.8up to date
 schemars^1.0.11.0.3up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 sse-stream^0.20.2.1up to date
 thiserror^22.0.12up to date
 tokio ⚠️^11.45.1maybe insecure
 tokio-stream^0.10.1.17up to date
 tokio-util^0.70.7.15up to date
 tower-service^0.30.3.3up to date
 tracing^0.10.1.41up to date
 url^2.42.5.4up to date
 uuid^11.17.0up to date

Dev dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.98up to date
 async-trait^0.10.1.88up to date
 schemars^1.0.11.0.3up to date
 tokio ⚠️^11.45.1maybe insecure
 tracing-subscriber^0.30.3.19up 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);