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 esbuild_client

Dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.981.0.98up to date
 async-trait^0.1.880.1.88up to date
 deno_unsync^0.4.20.4.4up to date
 derive_builder^0.20.20.20.2up to date
 indexmap^2.9.02.9.0up to date
 log^0.4.270.4.27up to date
 parking_lot^0.12.30.12.4up to date
 paste^1.0.151.0.15up to date
 serde^1.0.2191.0.219up to date
 tokio ⚠️^11.45.1maybe insecure

Dev dependencies

(10 total, 1 possibly insecure)

CrateRequiredLatestStatus
 directories^6.0.06.0.0up to date
 flate2^1.1.11.1.2up to date
 pathdiff^0.2.30.2.3up to date
 pretty_assertions^1.4.11.4.1up to date
 pretty_env_logger^0.5.00.5.0up to date
 serde_json^1.0.1401.0.140up to date
 sys_traits^0.1.140.1.16up to date
 tar^0.4.440.4.44up to date
 tokio ⚠️^11.45.1maybe insecure
 ureq^3.0.113.0.12up 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);