compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in compose-lint 0.33.0 and tmatens/compose-lint 0.33.0.
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.32.0 until 0.33.0, compose-lint's incomplete remediation for .env secret disclosure checks the 20,000-finding limit before replacing resolved values with their variable references. A pull request can combine a secret-referencing image field with aliased content that produces more than 20,000 findings, causing the early-stop path to emit already graded findings with the resolved secret value in text, JSON, SARIF, and Code Scanning output. Exploitation requires a workflow that writes secrets into the sibling .env and lints untrusted changes, and the run exits 2 unless --allow-partial-coverage is used. This issue is fixed in version 0.33.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| tmatens | >=0.32.0 <0.33.0 | ||
| pypi: compose-lint | =0.32.0, >=0.32.0 <0.33.0 | 0.33.0 | |
| actions: tmatens/compose-lint | =0.32.0 | 0.33.0 | |
| github actions: tmatens/compose-lint | >=0.32.0 <0.33.0 | 0.33.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in tmatens/compose-lint (GitHub Actions), strongest first
Embed
A live severity badge for an advisory, README or ticket