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

(18 total, 6 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 serde^1.01.0.215up to date
 serde_derive^1.01.0.215up to date
 serde_json^1.01.0.132up to date
 indexmap^1.62.6.0out of date
 rand^0.80.8.5up to date
 getrandom^0.20.2.15up to date
 num^0.40.4.3up to date
 csv^1.11.3.1up to date
 regex ⚠️^1.31.11.1maybe insecure
 lazy_static^1.41.5.0up to date
 packed_simd_2^0.30.3.8up to date
 chrono ⚠️^0.40.4.38maybe insecure
 flatbuffers ⚠️=2.0.024.3.25out of date
 hex^0.40.4.3up to date
 comfy-table^4.07.1.3out of date
 lexical-core^0.71.0.2out of date
 multiversion^0.6.10.7.4out of date
 bitflags^1.2.12.6.0out of date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.30.5.1out of date
 flate2^11.0.35up to date
 rand^0.80.8.5up to date
 tempfile^33.14.0up to date

Crate parquet

Dependencies

(17 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 parquet-format~4.0.04.0.0up to date
 aes-gcm^0.10.30.10.3up to date
 byteorder^11.5.0up to date
 thrift^0.130.17.0out of date
 snap^1.01.1.1up to date
 brotli^3.37.0.0out of date
 flate2^1.01.0.35up to date
 lz4^1.231.28.0up to date
 zstd^0.120.13.2out of date
 chrono ⚠️^0.40.4.38maybe insecure
 num-bigint^0.40.4.6up to date
 base64^0.130.22.1out of date
 clap^2.33.34.5.21out of date
 serde_json^1.01.0.132up to date
 serde^1.0.1151.0.215up to date
 rand^0.80.8.5up to date
 sha3^0.10.80.10.8up to date

Dev dependencies

(7 total, 2 outdated)

CrateRequiredLatestStatus
 criterion^0.30.5.1out of date
 rand^0.80.8.5up to date
 snap^1.01.1.1up to date
 brotli^3.37.0.0out of date
 flate2^1.01.0.35up to date
 lz4^1.231.28.0up to date
 serde_json^1.01.0.132up to date

Crate parquet_derive

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 proc-macro2^1.01.0.89up to date
 quote^1.01.0.37up to date
 syn^1.02.0.87out of date

Crate parquet_derive_test

No external dependencies! 🙌

Crate arrow-flight

Dependencies

(6 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.130.22.1out of date
 tonic^0.40.12.3out of date
 bytes^11.8.0up to date
 prost^0.70.13.3out of date
 prost-derive^0.70.13.3out of date
 tokio ⚠️^1.01.41.1maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 futures^0.30.3.31up to date

Build dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 tonic-build^0.40.12.3out of date
 proc-macro2^1.0.271.0.89up to date

Crate arrow-integration-testing

Dependencies

(11 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.410.1.83up to date
 clap^2.334.5.21out of date
 futures^0.30.3.31up to date
 hex^0.40.4.3up to date
 prost^0.70.13.3out of date
 serde^1.01.0.215up to date
 serde_derive^1.01.0.215up to date
 serde_json^1.01.0.132up to date
 tokio ⚠️^1.01.41.1maybe insecure
 tonic^0.40.12.3out of date
 tracing-subscriber^0.2.150.3.18out of date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

flatbuffers: Generated code can read and write out of bounds in safe code

RUSTSEC-2021-0122

Code generated by flatbuffers' compiler is unsafe but not marked as such. See https://github.com/google/flatbuffers/issues/6627 for details.

For example, if generated code is used to decode malformed or untrusted input, undefined behavior (and thus security vulnerabilities) is possible even without the use of the unsafe keyword, violating the the meaning of "safe" code;

All users that use generated code by flatbuffers compiler are recommended to:

  1. not expose flatbuffer generated code as part of their public APIs
  2. audit their code and look for any usage of follow, push, or any method that uses them (e.g. self_follow).
  3. Carefully go through the crates' documentation to understand which "safe" APIs are not intended to be used.

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.

Overview

The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.

Mitigations

We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.

Acknowledgements

We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.

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