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-core

Dependencies

(30 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrow-array^56.157.1.0out of date
 arrow-buffer^56.157.1.0out of date
 arrow-schema^56.157.1.0out of date
 async-trait^0.10.1.89up to date
 byteorder^1.51.5.0up to date
 bytes^1.41.11.0up to date
 chrono^0.4.410.4.42up to date
 datafusion-common^50.0.051.0.0out of date
 datafusion-sql^50.0.051.0.0out of date
 deepsize^0.2.00.2.0up to date
 futures^0.30.3.31up to date
 lance-arrow=0.38.30.39.0out of date
 libc^0.2.1760.2.178up to date
 log^0.40.4.29up to date
 mock_instant^0.6.00.6.0up to date
 moka^0.120.12.11up to date
 num_cpus^1.01.17.0up to date
 object_store^0.12.30.12.4up to date
 pin-project^1.01.1.10up to date
 prost^0.13.20.14.1out of date
 rand^0.9.10.9.2up to date
 roaring^0.10.10.11.3out of date
 serde_json^11.0.145up to date
 snafu^0.80.8.9up to date
 tempfile^33.23.0up to date
 tokio ⚠️^1.231.48.0maybe insecure
 tokio-stream^0.1.140.1.17up to date
 tokio-util^0.7.100.7.17up to date
 tracing^0.10.1.43up to date
 url^2.5.72.5.7up to date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 lance-testing=0.38.30.39.0out of date
 proptest^1.3.11.9.0up 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);