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 localcache

Dependencies

(18 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aes-gcm^0.10.30.10.3up to date
 async-std^1.131.13.2up to date
 base64^0.22.10.22.1up to date
 bincode^23.0.0out of date
 blake3^11.8.5up to date
 metrics^0.240.24.6up to date
 notify^88.2.0up to date
 notify-debouncer-mini^0.70.7.0up to date
 opentelemetry^0.320.32.0up to date
 rusqlite^0.400.40.1up to date
 serde^11.0.228up to date
 serde_json^11.0.150up to date
 smol^22.0.2up to date
 thiserror^22.0.18up to date
 tokio ⚠️^1.231.52.3maybe insecure
 tracing^0.10.1.44up to date
 tracing-opentelemetry^0.330.33.0up to date
 zstd^0.130.13.3up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.80.8.2up to date
 tempfile^33.27.0up to date
 tokio ⚠️^1.231.52.3maybe 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);