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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

• CVE-2024-41178: 0.71% estimated exploitation activity in the next 30 days; percentile 53.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Exposure of temporary credentials in logs in Apache Arrow Rust Object Store (objectstore crate), 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 https://docs.aws.amazon.com/STS/latest/APIReference/APIAssumeRoleWithWebIdentity.html . 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 objectstore 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…

Published by the source

23 Jul 2024, 18:31 UTC

Last modified by the source

3 Aug 2024, 05:06 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c2hf-vcmr-qjrf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-41178

Advisory: Apache Arrow Rust Object Store: AWS WebIdentityToken exposure in log files
IDs: CVE-2024-41178, GHSA-c2hf-vcmr-qjrf
Record: https://patchnext.com/advisories/cve-2024-41178 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: object_store 0.10.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io object_store: affected >= 0.5.0, < 0.10.2; fixed in 0.10.2

## Suggested inspection (read-only)
- crates.io object_store: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on object_store.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c2hf-vcmr-qjrf (GitHub-reviewed advisory GHSA-c2hf-vcmr-qjrf lists affected ranges: crates.io object_store >=0.5.0 <0.10.2)

Commands are suggestions: review each one before running it.