Secret disclosure via unrestricted pipeline substitution
Published Mar 12, 2024 · Updated Aug 2, 2024
Secret exposure in Vela Worker before 0.23.2 allows remote authenticated users to disclose protected secrets through pipeline substitution. The worker's Linux executor placed every loaded secret into the substitution map before container creation, even when allow_substitution was false. Exploitation requires pipeline-author access, a no-substitution secret supplied to a plugin or image field, and output that logs the transformed value.
Summary
What happened
Secret exposure in Vela Worker before 0.23.2 allows remote authenticated users to disclose protected secrets through pipeline substitution. The worker's Linux executor placed every loaded secret into the substitution map before container creation, even when allow_substitution was false. Exploitation requires pipeline-author access, a no-substitution secret supplied to a plugin or image field, and output that logs the transformed value.
The record
- CVE
- CVE-2024-28236
- Published
- Mar 12, 2024
- Updated
- Aug 2, 2024
- Vendor
- Vela
- Product
- Vela Worker
- Classifications
- CWE-532, CWE-200, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 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.23.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
- Upstream pipeline-substitution examplesproof 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