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 arrow Dependencies (2 total, all up-to-date)
Crate Required Latest Status rand ^0.90.9.2up to date half ^2.12.7.1up to date
Dev dependencies (5 total, all up-to-date)
Crate Required Latest Status half ^2.12.7.1up to date rand ^0.90.9.2up to date serde ^1.01.0.228up to date memmap2 ^0.9.30.9.9up to date bytes ^1.91.11.0up to date
Crate arrow-arith Dependencies (1 total, all up-to-date)
Crate Required Latest Status num-traits ^0.2.190.2.19up to date
Crate arrow-array Dependencies (7 total, all up-to-date)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status rand ^0.90.9.2up to date
Crate arrow-avro Dependencies (14 total, all up-to-date)
Crate Required Latest Status serde_json ^1.01.0.147up to date serde ^1.0.1881.0.228up to date flate2 ^1.01.1.5up to date snap ^1.01.1.1up to date zstd ^0.130.13.3up to date bzip2 ^0.6.00.6.1up to date liblzma ^0.40.4.5up to date crc ^3.03.4.0up to date strum_macros ^0.270.27.2up to date uuid ^1.171.19.0up to date indexmap ^2.102.12.1up to date rand ^0.90.9.2up to date md5 ^0.80.8.0up to date sha2 ^0.100.10.9up to date
Dev dependencies (8 total, all up-to-date)
Crate arrow-buffer Dependencies (4 total, all up-to-date)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status rand ^0.90.9.2up to date
Crate arrow-cast Dependencies (7 total, all up-to-date)
Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status half ^2.12.7.1up to date rand ^0.90.9.2up to date
Crate arrow-csv Dependencies (3 total, all up-to-date)
Crate Required Latest Status csv ^1.11.4.0up to date csv-core ^0.10.1.13up to date regex ^1.7.01.12.2up to date
Dev dependencies (4 total, all up-to-date)
Crate Required Latest Status tempfile ^3.33.24.0up to date futures ^0.30.3.31up to date tokio ^1.271.48.0up to date bytes ^1.41.11.0up to date
Crate arrow-data Dependencies (3 total, all up-to-date)
Crate arrow-flight Dependencies (14 total, 2 possibly insecure)
Dev dependencies (12 total, 2 possibly insecure)
Crate gen Dependencies (2 total, all up-to-date)
Crate arrow-integration-test Dependencies (5 total, all up-to-date)
Crate arrow-integration-testing Dependencies (8 total, 2 possibly insecure)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status tempfile ^33.24.0up to date
Crate arrow-ipc Dependencies (3 total, all up-to-date)
Crate Required Latest Status flatbuffers ^25.2.1025.12.19up to date lz4_flex ^0.120.12.0up to date zstd ^0.13.00.13.3up to date
Dev dependencies (4 total, all up-to-date)
Crate Required Latest Status tempfile ^3.33.24.0up to date tokio ^1.43.01.48.0up to date memmap2 ^0.9.30.9.9up to date bytes ^1.91.11.0up to date
Crate arrow-json Dependencies (9 total, all up-to-date)
Dev dependencies (6 total, all up-to-date)
Crate Required Latest Status flate2 ^11.1.5up to date serde ^1.01.0.228up to date futures ^0.30.3.31up to date tokio ^1.271.48.0up to date bytes ^1.41.11.0up to date rand ^0.90.9.2up to date
Crate arrow-ord Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status half ^2.12.7.1up to date rand ^0.90.9.2up to date
Crate arrow-pyarrow Dependencies (1 total, 1 outdated)
Crate Required Latest Status pyo3 ^0.26.00.27.2out of date
Crate arrow-row Dependencies (1 total, all up-to-date)
Crate Required Latest Status half ^2.12.7.1up to date
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status rand ^0.90.9.2up to date
Crate arrow-schema Dependencies (4 total, all up-to-date)
Dev dependencies (2 total, 1 outdated)
Crate Required Latest Status bincode ^2.0.13.0.0out of date insta ^1.43.11.45.0up to date
Crate arrow-select Dependencies (2 total, all up-to-date)
Crate Required Latest Status num-traits ^0.2.190.2.19up to date ahash ^0.80.8.12up to date
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status rand ^0.90.9.2up to date
Crate arrow-string Dependencies (4 total, all up-to-date)
Crate parquet Dependencies (25 total, 1 outdated, 2 possibly insecure)
Dev dependencies (13 total, 1 outdated, 1 possibly insecure)
Crate parquet-geospatial Dependencies (4 total, all up-to-date)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status wkt ^0.140.14.0up to date
Crate parquet-variant Dependencies (3 total, all up-to-date)
Crate Required Latest Status half ^2.12.7.1up to date indexmap ^2.10.02.12.1up to date uuid ^1.18.01.19.0up to date
Dev dependencies (2 total, all up-to-date)
Crate Required Latest Status paste ^1.01.0.15up to date rand ^0.90.9.2up to date
Crate parquet-variant-compute Dependencies (3 total, all up-to-date)
Crate Required Latest Status half ^2.12.7.1up to date indexmap ^2.10.02.12.1up to date uuid ^1.18.01.19.0up to date
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status rand ^0.9.10.9.2up to date
Crate parquet-variant-json Dependencies (3 total, all up-to-date)
Crate Required Latest Status serde_json ^1.01.0.147up to date base64 ^0.220.22.1up to date uuid ^1.18.01.19.0up to date
Crate parquet_derive Dependencies (3 total, all up-to-date)
Crate Required Latest Status proc-macro2 ^1.01.0.103up to date quote ^1.01.0.42up to date syn ^2.02.0.111up to date
Crate parquet_derive_test Dependencies (1 total, all up-to-date)
Crate Required Latest Status uuid ^11.19.0up to date
Security Vulnerabilities tokio: reject_remote_clients Configuration corruptionRUSTSEC-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);
Patched
>=1.18.4, <1.19.0
>=1.20.3, <1.21.0
>=1.23.1
ring: Some AES functions may panic when overflow checking is enabled.RUSTSEC-2025-0009
ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow
checking is enabled. In the QUIC protocol, an attacker can induce this panic by
sending a specially-crafted packet. Even unintentionally it is likely to occur
in 1 out of every 2**32 packets sent and/or received.
On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may
panic when overflow checking is enabled, when encrypting/decrypting approximately
68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols
like TLS and SSH are not affected by this because those protocols break large
amounts of data into small chunks. Similarly, most applications will not
attempt to encrypt/decrypt 64GB of data in one chunk.
Overflow checking is not enabled in release mode by default, but
RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml
profile can override this. Overflow checking is usually enabled by default in
debug mode.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesRUSTSEC-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.
