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 async-stomp

Dependencies

(11 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.100up to date
 bytes^1.10.11.11.0up to date
 custom_debug_derive^0.6.20.6.2up to date
 futures^0.30.3.31up to date
 rustls^0.23.310.23.36up to date
 tokio ⚠️^11.49.0maybe insecure
 tokio-rustls^0.26.20.26.4up to date
 tokio-util^0.70.7.18up to date
 typed-builder^0.21.00.23.2out of date
 webpki-roots^1.0.21.0.5up to date
 winnow^0.70.7.14up to date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.49.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);