compose-lint secret exposure in finding-limit handling
tmatens compose-lint
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| compose-lint PyPI |
|
|
| tmatens/compose-lint GitHub Actions |
|
|
tmatens compose-lint
| Product | Affected | Fixed in |
|---|---|---|
| compose-lint PyPI |
|
|
| tmatens/compose-lint GitHub Actions |
|
|
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.
From the CVE record · GitHub_M
In affected versions, compose-lint can include resolved .env secrets in text, JSON, SARIF, and Code Scanning findings when a pull request triggers more than 20,000 findings. This requires a workflow that writes secrets to the sibling .env file and lints untrusted changes; the run exits 2 unless --allow-partial-coverage is used.
Teams using the PyPI compose-lint package or tmatens/compose-lint GitHub Action at versions >=0.32.0 and <0.33.0 should check their workflows.