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 hdfs-native

Dependencies

(20 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.210.22.1out of date
 bytes^11.6.0up to date
 crc^33.2.1up to date
 futures^0.30.3.30up to date
 g2p^11.0.1up to date
 gsasl-sys^0.20.2.4up to date
 libc^0.20.2.155up to date
 libgssapi^0.60.7.0out of date
 log^0.40.4.21up to date
 num-traits^0.20.2.19up to date
 prost^0.110.12.6out of date
 prost-types^0.110.12.6out of date
 roxmltree^0.180.19.0out of date
 socket2^0.50.5.7up to date
 thiserror^11.0.61up to date
 tokio ⚠️^11.37.0maybe insecure
 url^22.5.0up to date
 users^0.110.11.0up to date
 uuid^11.8.0up to date
 which^46.0.1out of date

Dev dependencies

(5 total, 3 outdated)

CrateRequiredLatestStatus
 criterion^0.50.5.1up to date
 env_logger^0.100.11.3out of date
 serial_test^2.0.03.1.1out of date
 tempfile^33.10.1up to date
 which^46.0.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);