compose-lint data exposure in .env symlink 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.22.0 until 0.31.0, compose-lint follows a sibling .env symbolic link outside the project without applying its normal containment check. From 0.28.0, the same gap also affects an include project_directory link outside the project. A pull request can reference a variable from the linked file, causing substitution to place runner file or process-environment data into finding messages written to logs, JSON, SARIF artifacts, and Code Scanning alerts. Reading /proc/self/environ can expose the remainder of the linter process environment because NUL-separated entries are treated as one value, although disclosure requires a workflow that processes untrusted changes with useful environment data and GitHub normally withholds secrets from fork pull requests. The pass or fail result is not changed. This issue is fixed in version 0.31.0.
From the CVE record · GitHub_M
compose-lint can follow a sibling .env symlink outside the project; from 0.28.0, the same issue affects an include project_directory link. An attacker who can submit a pull request may cause runner file or process-environment data to appear in findings, logs, and artifacts if a workflow processes untrusted changes with useful environment data. GitHub normally withholds secrets from fork pull requests.
Teams using PyPI compose-lint or the tmatens/compose-lint GitHub Action at versions >=0.22.0 and <0.31.0 should check their workflows.