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 toxicblend

Dependencies

(19 total, 12 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.70.8.11out of date
 boostvoronoi^0.100.11.1out of date
 bytemuck^1.71.15.0up to date
 centerline^0.70.11.0out of date
 cgmath^0.180.18.0up to date
 fast-surface-nets^0.10.2.0out of date
 glam^0.180.27.0out of date
 ilattice^0.10.4.0out of date
 itertools^0.100.12.1out of date
 linestring^0.80.13.0out of date
 logos^0.120.14.0out of date
 prost^0.90.12.3out of date
 rayon^1.51.10.0up to date
 saft^0.260.34.1out of date
 smallvec^1.71.13.2up to date
 thiserror^1.01.0.58up to date
 tokio ⚠️^1.141.37.0maybe insecure
 tonic^0.60.11.0out of date
 vob^3.03.0.3up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.30.5.1out of 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);