S3 credential exposure via plaintext support bundles
Published Oct 21, 2022 · Updated May 7, 2025
Credential exposure in Gradle Enterprise 2022.3 through 2022.3.2 allows remote attackers to obtain S3 access credentials from support bundles. The support-bundle generator writes configured Amazon S3-compatible object-store access credentials into the bundle in plaintext, enabling direct reads and writes of Build Scan data. Exposure requires an administrator to generate and share a bundle from an installation using credential-based S3 storage; instance-profile authentication and non-S3 storage are unaffected.
Summary
What happened
Credential exposure in Gradle Enterprise 2022.3 through 2022.3.2 allows remote attackers to obtain S3 access credentials from support bundles. The support-bundle generator writes configured Amazon S3-compatible object-store access credentials into the bundle in plaintext, enabling direct reads and writes of Build Scan data. Exposure requires an administrator to generate and share a bundle from an installation using credential-based S3 storage; instance-profile authentication and non-S3 storage are unaffected.
The record
- CVE
- CVE-2022-41575
- Published
- Oct 21, 2022
- Updated
- May 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 21, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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