dbcve.org
ArrowApplication · Apache

CVE-2024-41178

HIGH · 7.5 CVSS v3.1 Published 2024-07-23
Fix available
A fix is available. Upgrade to after 0.10.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of temporary credentials in logs in Apache Arrow Rust Object Store (`object_store` 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/API_AssumeRoleWithWebIdentity.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 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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The object_store crate (versions 0.10.1 and earlier) writes sensitive OIDC tokens to logs during error conditions when using AWS WebIdentityTokens authentication. When a failure occurs and triggers a retry, the underlying reqwest error containing the full URL with credentials is logged, exposing temporary credentials that allow impersonation for up to an hour.

MitigationUpgrade to version 0.10.2 which fixes the credential logging, or alternatively use a different AWS authentication mechanism or disable logging to prevent credential exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArrowApplication
Affected:>= 0.5.0, <= 0.10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify object_store crate usage
    Search your codebase (Cargo.toml, Cargo.lock, or dependency files) for the object_store crate dependency and note its version.
    Affected if The object_store crate version is 0.10.1 or earlier (any version from 0.5.0 to 0.10.1 inclusive).
  2. Confirm AWS WebIdentityToken authentication
    Check your environment or configuration for AWS WebIdentityToken-related variables: AWS_WEB_IDENTITY_TOKEN_FILE, AWS_ROLE_ARN, and AWS_WEB_IDENTITY_TOKEN. Also review your object_store or AWS SDK configuration for WebIdentityTokens authentication method.
    Affected if AWS WebIdentityToken authentication is configured or environment variables for it are set.
  3. Verify logging is active
    Review your application's logging configuration (log4j, logback, env_logger, tracing, or similar) to confirm that error-level logging is enabled and that logs are being written to a destination (file, stdout, cloud logging).
    Affected if Logging at error level is enabled and logs are persisted or transmitted.

You are affected if your application uses the object_store crate version 0.10.1 or earlier with AWS WebIdentityToken authentication and error-level logging is enabled, as credentials may have been exposed in logs during retry failures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.10.1
Interim mitigation

Upgrade to version 0.10.2 which fixes the credential logging, or alternatively use a different AWS authentication mechanism or disable logging to prevent credential exposure.

Recommended fix High confidence

object_store crate version 0.10.2

  1. Update the object_store crate dependency in your Cargo.toml to version 0.10.2 or later
  2. Run cargo update object_store to fetch the updated version
  3. Rebuild your project with cargo build to verify the update
  4. Review your application logs to confirm sensitive credentials are no longer being written
Caveat Review the object_store changelog between 0.10.1 and 0.10.2 for any API changes that may affect your implementation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arrow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41178 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data