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 expiring-bloom-rs

Dependencies

(21 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bincode^22.0.1up to date
 fnv^11.0.7up to date
 murmur3^0.50.5.2up to date
 thiserror^22.0.12up to date
 derive_builder^0.200.20.2up to date
 tracing-subscriber^0.30.3.19up to date
 tracing^0.10.1.41up to date
 bitvec^11.0.1up to date
 serde^11.0.219up to date
 dotenvy^0.150.15.7up to date
 axum^0.80.8.4up to date
 tokio ⚠️^11.47.1maybe insecure
 utoipa^5.35.4.0up to date
 utoipa-swagger-ui^99.0.2up to date
 serde_json^11.0.142up to date
 clap^4.54.5.42up to date
 ratatui^0.290.29.0up to date
 unicode-width^0.20.2.1up to date
 redb^22.6.2up to date
 fjall^2.82.11.2up to date
 async-trait^0.1.880.1.88up to date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 rand^0.90.9.2up to date
 criterion^0.50.7.0out of date
 tower^0.50.5.2up to date
 comfy-table^7.17.1.4up to date
 colored^3.03.0.0up to date
 tokio ⚠️^11.47.1maybe 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);