Credential disclosure via unredacted repository URLs
Published Jun 3, 2024 · Updated Sep 3, 2024
Credential exposure in Chainguard apko before 0.14.5 allows attackers to read HTTP basic authentication secrets from build logs. Log and error paths format URL values directly or serialize repository and keyring strings without first parsing and redacting embedded user information. Exposure requires Basic Auth URLs and access to debug, CI, internal, or public logs; the reported consequence is plaintext credential disclosure.
Summary
What happened
Credential exposure in Chainguard apko before 0.14.5 allows attackers to read HTTP basic authentication secrets from build logs. Log and error paths format URL values directly or serialize repository and keyring strings without first parsing and redacting embedded user information. Exposure requires Basic Auth URLs and access to debug, CI, internal, or public logs; the reported consequence is plaintext credential disclosure.
The record
- CVE
- CVE-2024-36127
- Published
- Jun 3, 2024
- Updated
- Sep 3, 2024
- Vendor
- Chainguard
- Product
- apko
- Classifications
- CWE-532, CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 3, 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 <0.14.5
- Affected versionversion=< 0.14.5
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
- Upstream plaintext credential disclosure PoCproof of concept · demonstrated
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