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 walkers

Dependencies

(18 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 earcut^0.4.40.4.4up to date
 egui^0.330.33.3up to date
 egui_extras^0.330.33.3up to date
 flate2^1.1.41.1.5up to date
 futures^0.3.310.3.31up to date
 geo-types^0.70.7.18up to date
 http-cache-reqwest^0.16.00.16.0up to date
 image^0.250.25.9up to date
 log^0.40.4.29up to date
 lru^0.160.16.2up to date
 mvt-reader^2.1.02.2.0up to date
 pmtiles^0.16.00.18.2out of date
 reqwest^0.120.12.25up to date
 reqwest-middleware^0.4.20.4.2up to date
 serde^11.0.228up to date
 thiserror^22.0.17up to date
 tokio ⚠️^11.48.0maybe insecure
 wasm-bindgen-futures^0.40.4.56up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 approx^0.50.5.1up to date
 eframe^0.330.33.3up to date
 env_logger^0.110.11.8up 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);