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

(18 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.30.3.5up to date
 base64^0.210.22.1out of date
 bytes^11.6.0up to date
 futures^0.30.3.30up to date
 http^1.01.1.0up to date
 http-body^1.01.0.0up to date
 http-body-util^0.10.1.1up to date
 http-serde^2.02.1.0up to date
 hyper^1.01.3.1up to date
 hyper-util^0.1.10.1.3up to date
 lambda_runtime_api_client^0.100.11.1out of date
 serde^11.0.201up to date
 serde_json^11.0.117up to date
 serde_path_to_error^0.1.110.1.16up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tokio-stream^0.1.20.1.15up to date
 tower^0.40.4.13up to date
 tracing^0.10.1.40up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 httpmock^0.7.00.7.0up to date
 hyper-util^0.1.10.1.3up to date
 pin-project-lite^0.20.2.14up 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);