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 trotter

Dependencies

(9 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 clap^44.5.21up to date
 mime_guess^22.0.5up to date
 openssl ⚠️^0.100.10.68maybe insecure
 thiserror^1.02.0.3out of date
 tokio ⚠️^11.41.1maybe insecure
 tokio-openssl^0.60.6.5up to date
 url^2.42.5.3up to date
 urlencoding^2.1.32.1.3up to date
 wildmatch^2.1.12.4.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^11.0.93up to date
 clap^44.5.21up 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);

openssl: `MemBio::get_buf` has undefined behavior with empty buffers

RUSTSEC-2024-0357

Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.