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.
datafusion-common(9 total, 7 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| apache-avro | ^0.14 | 0.17.0 | out of date |
| arrow | ^34.0.0 | 53.2.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| cranelift-module | ^0.92.0 | 0.113.1 | out of date |
| num_cpus | ^1.13.0 | 1.16.0 | up to date |
| object_store ⚠️ | ^0.5.4 | 0.11.1 | out of date |
| parquet | ^34.0.0 | 53.2.0 | out of date |
| pyo3 | ^0.18.0 | 0.23.1 | out of date |
| sqlparser | ^0.32 | 0.52.0 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
object_store: Apache Arrow Rust Object Store: AWS WebIdentityToken exposure in log filesExposure 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.
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