compose-lint file data exposure in Compose symlink 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.25.0, compose-lint follows a project-controlled symbolic link used as the Compose file outside the project. The same issue affects compose.override.yml and a COMPOSE_FILE entry from 0.22.0, and an env_file target from 0.23.0. If an external Compose-related target fails YAML parsing, the error quotes an attacker-uncontrolled line into standard error, JSON errors, and SARIF notifications, while an external env_file can expose credential-like key names through CL-0020 and CL-0021 findings. The attacker selects the target path but not the exact parser-failure line, values from env_file are not printed, and the pass or fail result is unchanged. This issue is fixed in version 0.25.0.
From the CVE record · GitHub_M
Affected compose-lint versions follow project-controlled symbolic links for Compose-related files outside the project. If an external Compose-related target fails YAML parsing, error output can quote a line from that file; an external env_file can expose credential-like key names in findings. An attacker can select the target path but not the exact line quoted, and env_file values are not printed.
Teams using the PyPI compose-lint package or tmatens/compose-lint GitHub Action from version 0.2.0 up to, but not including, 0.25.0 should check their deployments.