compose-lint file data exposure in policy-file parsing
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.2.0 until 0.32.0, compose-lint automatically follows a .compose-lint.yml policy-file symbolic link outside the project and includes part of the target line when that external file fails YAML parsing. A pull request can point the policy file at a runner credential file, causing about 30 characters around an attacker-uncontrolled parse position to appear in standard error, JSON errors, and SARIF tool execution notifications uploaded by the GitHub Action. The run exits with an error and the attacker cannot select the exact disclosed line, but public logs or Code Scanning output can reveal part of the target. This issue is fixed in version 0.32.0.
From the CVE record · GitHub_M
Before version 0.32.0, compose-lint follows .compose-lint.yml symbolic links outside the project and can include part of the target file in YAML parse errors. An attacker who can submit a pull request can link the policy file to a runner credential file; if parsing fails, public logs or Code Scanning output may reveal part of that file. The attacker cannot choose the exact disclosed line.
Teams using the PyPI compose-lint package or tmatens/compose-lint GitHub Action at versions >=0.2.0 and <0.32.0 should check their installations.