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 lance-datafusion

Dependencies

(25 total, 15 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrow^57.0.058.1.0out of date
 arrow-array^57.0.058.1.0out of date
 arrow-buffer^57.0.058.1.0out of date
 arrow-ord^57.0.058.1.0out of date
 arrow-schema^57.0.058.1.0out of date
 arrow-select^57.0.058.1.0out of date
 async-trait^0.10.1.89up to date
 chrono^0.4.410.4.44up to date
 datafusion^52.1.053.1.0out of date
 datafusion-common^52.1.053.1.0out of date
 datafusion-functions^52.1.053.1.0out of date
 datafusion-physical-expr^52.1.053.1.0out of date
 datafusion-substrait^52.1.053.1.0out of date
 futures^0.30.3.32up to date
 jsonb^0.5.30.5.6up to date
 lance-arrow=3.0.14.0.0out of date
 lance-core=3.0.14.0.0out of date
 lance-datagen=3.0.14.0.0out of date
 lance-geo=3.0.14.0.0out of date
 log^0.40.4.29up to date
 pin-project^1.01.1.11up to date
 prost^0.14.10.14.3up to date
 snafu^0.90.9.0up to date
 tokio ⚠️^1.231.52.1maybe insecure
 tracing^0.10.1.44up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 lance-datagen=3.0.14.0.0out 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);