Cloud registry credential exposure via permissive domain checks
Published May 20, 2024 · Updated Aug 2, 2024
Credential exposure in Aqua Security Trivy before 0.51.2 allows attackers to obtain cloud registry tokens through a crafted registry. Registry checks accepted attacker-controlled domains ending in broad cloud-provider strings, causing Trivy to acquire and send credentials to lookalike hosts. Exploitation requires a direct registry image scan while the default credential provider chain can return valid AWS, Google Cloud, or Azure credentials.
Summary
What happened
Credential exposure in Aqua Security Trivy before 0.51.2 allows attackers to obtain cloud registry tokens through a crafted registry. Registry checks accepted attacker-controlled domains ending in broad cloud-provider strings, causing Trivy to acquire and send credentials to lookalike hosts. Exploitation requires a direct registry image scan while the default credential provider chain can return valid AWS, Google Cloud, or Azure credentials.
The record
- CVE
- CVE-2024-35192
- Published
- May 20, 2024
- Updated
- Aug 2, 2024
- Vendor
- Aqua Security
- Product
- Trivy
- Classifications
- CWE-522, T1528
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.51.2
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