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 webrtc-srtp

Dependencies

(17 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aead^0.30.5.2out of date
 aes^0.6.00.8.4out of date
 aes-gcm^0.80.10.3out of date
 anyhow^1.0.411.0.82up to date
 async-trait^0.10.1.80up to date
 byteorder^1.3.21.5.0up to date
 bytes^11.6.0up to date
 ctr^0.6.00.9.2out of date
 hmac^0.10.10.12.1out of date
 log^0.40.4.21up to date
 rtcp^0.3.10.10.1out of date
 rtp^0.3.10.10.0out of date
 sha-1^0.9.10.10.1out of date
 subtle^2.1.12.5.0up to date
 thiserror^1.0.251.0.59up to date
 tokio ⚠️^11.37.0maybe insecure
 webrtc-util^0.4.10.8.1out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 lazy_static^1.41.4.0up to date
 tokio-test^0.40.4.4up 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);