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 pmtiles

Dependencies

(18 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-compression^0.40.4.36up to date
 async-stream^0.30.3.6up to date
 aws-sdk-s3^1.49.01.118.0up to date
 bytes^11.11.0up to date
 countio^0.2.190.2.19up to date
 fast_hilbert^2.0.12.0.2up to date
 flate2^11.1.5up to date
 fmmap^0.40.4.0up to date
 futures-util^0.30.3.31up to date
 object_store^0.120.12.4up to date
 reqwest^0.12.40.12.26up to date
 rust-s3^0.35.10.37.1out of date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 thiserror^22.0.17up to date
 tilejson^0.40.4.3up to date
 tokio ⚠️^11.48.0maybe insecure
 varint-rs^22.2.0up to date

Dev dependencies

(8 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 flate2^11.1.5up to date
 fmmap^0.40.4.0up to date
 httpmock^0.7.00.8.2out of date
 reqwest^0.12.40.12.26up to date
 rstest^0.26.10.26.1up to date
 tempfile^3.13.03.23.0up to date
 tokio ⚠️^11.48.0maybe insecure
 url^22.5.7up 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);