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 stun

Dependencies

(11 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 webrtc-util^0.5.40.9.0out of date
 tokio ⚠️^1.191.38.1maybe insecure
 lazy_static^1.41.5.0up to date
 url^2.22.5.2up to date
 rand^0.8.50.8.5up to date
 base64^0.13.00.22.1out of date
 subtle^2.42.6.1up to date
 crc^3.03.2.1up to date
 ring^0.16.200.17.8out of date
 md-5^0.10.10.10.6up to date
 thiserror^1.01.0.63up to date

Dev dependencies

(3 total, 2 outdated)

CrateRequiredLatestStatus
 tokio-test^0.4.00.4.4up to date
 clap^3.2.64.5.9out of date
 criterion^0.3.50.5.1out of 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);