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 lambda_runtime

Dependencies

(16 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.30.3.6up to date
 base64^0.20.00.22.1out of date
 bytes^1.01.10.1up to date
 futures^0.30.3.31up to date
 http^0.21.3.1out of date
 http-body^0.41.0.1out of date
 http-serde^1.1.32.1.1out of date
 hyper^0.14.201.6.0out of date
 lambda_runtime_api_client^0.80.11.1out of date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 serde_path_to_error^0.1.110.1.17up to date
 tokio ⚠️^1.01.45.0maybe insecure
 tokio-stream^0.1.20.1.17up to date
 tower^0.40.5.2out of date
 tracing^0.1.370.1.41up 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);