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 actix-telepathy

Dependencies

(22 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix=0.13.00.13.3out of date
 actix-broker^0.4.30.4.3up to date
 actix_telepathy_derive^0.3.10.3.4up to date
 byteorder^1.31.5.0up to date
 bytes^11.6.0up to date
 derive_more^0.990.99.17up to date
 env_logger^0.90.11.3out of date
 flexbuffers^2.0.02.0.0up to date
 futures^0.30.3.30up to date
 log^0.40.4.21up to date
 ndarray^0.15.40.15.6up to date
 once_cell^1.5.21.19.0up to date
 parking_lot^0.120.12.2up to date
 rand^0.80.8.5up to date
 serde^1.01.0.202up to date
 serde_derive^1.01.0.202up to date
 tokio ⚠️^1.181.37.0maybe insecure
 tokio-stream^0.10.1.15up to date
 tokio-util^0.70.7.11up to date
 trust-dns-proto^0.22.00.23.2out of date
 trust-dns-resolver^0.22.00.23.2out of date
 uuid^1.01.8.0up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 actix-rt^2.0.02.9.0up to date
 futures-sink^0.3.210.3.30up to date
 port_scanner^0.1.50.1.5up to date
 rayon^1.5.01.10.0up 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);