Temporary credential disclosure via unsanitized retry errors
Published Jul 23, 2024 · Updated Aug 13, 2024
Credential exposure in Apache Arrow Rust Object Store 0.5.0 through 0.10.1 allows local users to read OIDC tokens from logs. The automatic retry path logs the underlying reqwest error, including the full AssumeRoleWithWebIdentity URL and token parameters, without sanitization. Exploitation requires AWS WebIdentityTokens, a failed request followed by a retry, and access to application logs; the exposed token enables identity impersonation until it expires.
Summary
What happened
Credential exposure in Apache Arrow Rust Object Store 0.5.0 through 0.10.1 allows local users to read OIDC tokens from logs. The automatic retry path logs the underlying reqwest error, including the full AssumeRoleWithWebIdentity URL and token parameters, without sanitization. Exploitation requires AWS WebIdentityTokens, a failed request followed by a retry, and access to application logs; the exposed token enables identity impersonation until it expires.
The record
- CVE
- CVE-2024-41178
- Published
- Jul 23, 2024
- Updated
- Aug 13, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Arrow
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2024CVE publishedPublication date reported by the CVE source.
- Aug 13, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.5.0 <=0.10.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo