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

Dependencies

(60 total, 30 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-buffer^56.157.1.0out of date
 arrow-ipc^56.157.1.0out of date
 arrow-ord^56.157.1.0out of date
 arrow-row^56.157.1.0out of date
 arrow-schema^56.157.1.0out of date
 arrow-select^56.157.1.0out of date
 async-recursion^1.01.1.1up to date
 async-trait^0.10.1.89up to date
 async_cell^0.2.20.2.3up to date
 aws-credential-types^1.2.01.2.11up to date
 aws-sdk-dynamodb^1.38.01.101.0up to date
 byteorder^1.51.5.0up to date
 bytes^1.41.11.0up to date
 chrono^0.4.410.4.42up to date
 clap^4.1.14.5.53up to date
 dashmap^66.1.0up to date
 datafusion^50.0.051.0.0out of date
 datafusion-expr^50.0.051.0.0out of date
 datafusion-functions^50.0.051.0.0out of date
 datafusion-physical-expr^50.0.051.0.0out of date
 datafusion-physical-plan^50.0.051.0.0out of date
 deepsize^0.2.00.2.0up to date
 either^1.01.15.0up to date
 futures^0.30.3.31up to date
 half^2.12.7.1up to date
 humantime^2.2.02.3.0up to date
 itertools^0.130.14.0out of 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-encoding=0.38.30.39.0out of date
 lance-file=0.38.30.39.0out of date
 lance-index=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-namespace=0.38.30.39.0out of date
 lance-table=0.38.30.39.0out of date
 lapack^0.19.00.20.0out of date
 log^0.40.4.29up to date
 moka^0.120.12.11up to date
 object_store^0.12.30.12.4up to date
 permutation^0.4.00.4.1up to date
 pin-project^1.01.1.10up to date
 prost^0.12.60.14.1out of date
 prost-types^0.13.20.14.1out of date
 rand^0.9.10.9.2up to date
 roaring^0.10.10.11.2out 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
 tfrecord^0.15.00.15.0up to date
 tokio ⚠️^1.231.48.0maybe insecure
 tokio-stream^0.1.140.1.17up to date
 tracing^0.10.1.43up to date
 url^2.5.72.5.7up to date
 uuid^1.21.19.0up to date

Dev dependencies

(20 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 all_asserts^2.3.12.3.3up to date
 approx^0.5.10.5.1up to date
 aws-config^1.2.01.8.12up to date
 aws-sdk-s3^1.38.01.117.0up to date
 clap^44.5.53up to date
 criterion^0.50.8.1out of date
 dirs^5.0.06.0.0out of date
 env_logger^0.11.70.11.8up to date
 lance-datagen=0.38.30.39.0out of date
 lance-test-macros=0.38.30.39.0out of date
 lance-testing=0.38.30.39.0out of date
 lzma-sys^0.10.1.20up to date
 mock_instant^0.6.00.6.0up to date
 pprof^0.14.00.15.0out of date
 pretty_assertions^1.4.01.4.1up to date
 rstest^0.23.00.26.1out of date
 tempfile^33.23.0up to date
 test-log^0.2.150.2.19up to date
 tracing-chrome^0.7.10.7.2up to date
 tracing-subscriber ⚠️^0.3.170.3.22maybe insecure

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);

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.