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 eventsource-client

Dependencies

(8 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.3.210.3.31up to date
 hyper^0.14.191.5.1out of date
 hyper-rustls^0.24.10.27.3out of date
 hyper-timeout^0.4.10.5.2out of date
 log^0.4.60.4.22up to date
 pin-project^1.0.101.1.7up to date
 rand^0.8.50.8.5up to date
 tokio ⚠️^1.17.01.42.0maybe insecure

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.10.00.11.5out of date
 maplit^1.0.11.0.2up to date
 proptest^1.0.01.5.0up to date
 simplelog^0.12.10.12.2up to date
 test-case^3.2.13.3.1up to date
 tokio ⚠️^1.2.01.42.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);