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 cobble-core

Dependencies

(23 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 async_zip^0.0.90.0.17out of date
 derive_builder^0.120.20.2out of date
 futures^0.30.3.31up to date
 hex^0.40.4.3up to date
 parking_lot^0.120.12.3up to date
 reqwest^0.110.12.9out of date
 serde^1.01.0.216up to date
 serde_json^1.01.0.134up to date
 sha1^0.100.10.6up to date
 thiserror^1.02.0.9out of date
 time^0.30.3.37up to date
 tokio ⚠️^1.221.42.0maybe insecure
 tokio-stream^0.10.1.17up to date
 tracing^0.10.1.41up to date
 uuid^1.21.11.0up to date
 anyhow^1.01.0.94up to date
 base64^0.130.22.1out of date
 fastnbt^2.32.5.0up to date
 flate2^1.01.0.35up to date
 mime_guess^2.02.0.5up to date
 oauth2^4.34.4.2up to date
 tar>=0.4.360.4.43up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.94up to date
 tokio ⚠️^1.221.42.0maybe insecure
 tracing-subscriber^0.30.3.19up 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);