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 eszip

Dependencies

(11 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.82up to date
 base64^0.13.00.22.0out of date
 deno_ast^0.14.00.37.1out of date
 deno_graph^0.26.00.73.1out of date
 futures^0.3.190.3.30up to date
 serde^11.0.198up to date
 serde_json^11.0.116up to date
 sha2^0.10.10.10.8up to date
 thiserror^1.0.301.0.58up to date
 tokio ⚠️^11.37.0maybe insecure
 url^2.2.22.5.0up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 import_map^0.7.00.19.1out of date
 pretty_assertions^11.4.0up to date
 tokio ⚠️^11.37.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);