RUSTSEC-2024-0358: Apache Arrow Rust Object Store: AWS WebIdentityToken exposure in log files

What to do

1. See which version you have: cargo tree -i object_store (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p object_store. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example object_store = "0.10.2") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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

References

• Package: crates.io/crates/object_store
• Advisory: rustsec.org/advisories/RUSTSEC-2024-0358.html
• Web: github.com/apache/arrow-rs/pull/6074
• Web: www.openwall.com/lists/oss-security/2024/07/23/3

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.