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

Dependencies

(57 total, 28 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 arrow^56.157.1.0out of date
 arrow-arith^56.157.1.0out of date
 arrow-array^56.157.1.0out of date
 arrow-ord^56.157.1.0out of date
 arrow-schema^56.157.1.0out of date
 arrow-select^56.157.1.0out of date
 async-channel^2.3.12.5.0up to date
 async-recursion^1.01.1.1up to date
 async-trait^0.10.1.89up to date
 bitpacking^0.9.20.9.2up to date
 bitvec^11.0.1up to date
 bytes^1.41.11.0up to date
 crossbeam-queue^0.30.3.12up to date
 datafusion^50.0.051.0.0out of date
 datafusion-common^50.0.051.0.0out of date
 datafusion-expr^50.0.051.0.0out of date
 datafusion-physical-expr^50.0.051.0.0out of date
 datafusion-sql^50.0.051.0.0out of date
 deepsize^0.2.00.2.0up to date
 dirs^6.0.06.0.0up to date
 fst^0.4.70.4.7up to date
 futures^0.30.3.31up to date
 half^2.12.7.1up to date
 itertools^0.130.14.0out of date
 jieba-rs^0.8.10.8.1up to date
 jsonb^0.5.30.5.5up to date
 lance-arrow=0.38.30.39.0out of date
 lance-core=0.38.30.39.0out of date
 lance-datafusion=0.38.30.39.0out of date
 lance-datagen=0.38.30.39.0out of date
 lance-encoding=0.38.30.39.0out of date
 lance-file=0.38.30.39.0out of date
 lance-io=0.38.30.39.0out of date
 lance-linalg=0.38.30.39.0out of date
 lance-table=0.38.30.39.0out of date
 libm^0.2.150.2.15up to date
 lindera^0.44.01.4.1out of date
 lindera-tantivy^0.44.01.1.1out of date
 log^0.40.4.29up to date
 ndarray^0.16.10.17.1out of date
 num-traits^0.20.2.19up to date
 object_store^0.12.30.12.4up to date
 prost^0.13.20.14.1out of date
 prost-types^0.13.20.14.1out of date
 rand^0.9.10.9.2up to date
 rand_distr^0.5.10.5.1up to date
 rayon^1.101.11.0up to date
 roaring^0.10.10.11.3out of date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 snafu^0.80.8.9up to date
 tantivy^0.24.10.25.0out of date
 tempfile^33.23.0up to date
 tokio ⚠️^1.231.48.0maybe insecure
 tracing^0.10.1.43up to date
 twox-hash^2.02.1.2up to date
 uuid^1.21.19.0up to date

Dev dependencies

(9 total, 5 outdated)

CrateRequiredLatestStatus
 approx^0.5.10.5.1up to date
 chrono^0.4.410.4.42up to date
 criterion^0.50.8.1out of date
 env_logger^0.11.60.11.8up to date
 lance-datagen=0.38.30.39.0out of date
 lance-testing=0.38.30.39.0out of date
 pprof^0.14.00.15.0out of date
 rstest^0.23.00.26.1out of date
 test-log^0.2.150.2.19up 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);