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 datafusion-common

Dependencies

(18 total, 8 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 apache-avro^0.150.17.0out of date
 arrow^46.0.053.2.0out of date
 arrow-array^46.0.053.2.0out of date
 async-compression^0.4.00.4.17up to date
 bytes^1.41.8.0up to date
 bzip2 ⚠️^0.4.30.4.4maybe insecure
 chrono^0.4.270.4.38up to date
 flate2^1.0.241.0.35up to date
 futures^0.30.3.31up to date
 num_cpus^1.13.01.16.0up to date
 object_store ⚠️^0.7.00.11.1out of date
 parquet^46.0.053.2.0out of date
 pyo3^0.19.00.23.0out of date
 sqlparser^0.37.00.52.0out of date
 tokio^1.281.41.1up to date
 tokio-util^0.7.40.7.12up to date
 xz2^0.10.1.7up to date
 zstd^0.120.13.2out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 rand^0.8.40.8.5up to date

Security Vulnerabilities

bzip2: bzip2 Denial of Service (DoS)

RUSTSEC-2023-0004

Working with specific payloads can cause a Denial of Service (DoS) vector.

Both Decompress and Compress implementations can enter into infinite loops given specific payloads entered that trigger it.

The issue is described in great detail in the bzip2 repository issue.

Thanks to bjrjk for finding and providing the patch for the issue and the maintainer responsibly responding to release a fix quickly.

Users who use the crate with untrusted data should update the bzip2 to 0.4.4.

object_store: Apache Arrow Rust Object Store: AWS WebIdentityToken exposure in log files

RUSTSEC-2024-0358

Exposure of temporary credentials in logs in Apache Arrow Rust Object Store, version 0.10.1 and earlier on all platforms using AWS WebIdentityTokens.

On certain error conditions, the logs may contain the OIDC token passed to AssumeRoleWithWebIdentity. This allows someone with access to the logs to impersonate that identity, including performing their own calls to AssumeRoleWithWebIdentity, until the OIDC token expires. Typically OIDC tokens are valid for up to an hour, although this will vary depending on the issuer.

Users are recommended to use a different AWS authentication mechanism, disable logging or upgrade to version 0.10.2, which fixes this issue.

Details

When using AWS WebIdentityTokens with the object_store crate, in the event of a failure and automatic retry, the underlying reqwest error, including the full URL with the credentials, potentially in the parameters, is written to the logs.

Thanks to Paul Hatcherian for reporting this vulnerability