Command injection via crafted filenames in Super-linter Action
super-linter
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| super-linter/super-linter GitHub Actions |
|
|
| super-linter/super-linter/slim GitHub Actions |
|
|
super-linter
| Product | Affected | Fixed in |
|---|---|---|
| super-linter/super-linter GitHub Actions |
|
|
| super-linter/super-linter/slim GitHub Actions |
|
|
Super-linter is a combination of multiple linters to run as a GitHub Action or standalone. From 6.0.0 to 8.3.0, the Super-linter GitHub Action is vulnerable to command injection via crafted filenames. When this action is used in downstream GitHub Actions workflows, an attacker can submit a pull request that introduces a file whose name contains shell command substitution syntax, such as $(...). In affected Super-linter versions, runtime scripts may execute the embedded command during file discovery processing, enabling arbitrary command execution in the workflow runner context. This can be used to disclose the job’s GITHUB_TOKEN depending on how the workflow configures permissions. This vulnerability is fixed in 8.3.1.
From the CVE record · GitHub_M
The super-linter GitHub Action is vulnerable to command injection through crafted filenames during file discovery. An attacker who can submit a pull request to a downstream workflow using an affected version can cause commands embedded in a filename to run on the workflow runner. This may disclose the job’s GITHUB_TOKEN, depending on workflow permissions.
Check workflows using super-linter/super-linter or super-linter/super-linter/slim versions 6.0.0 through 8.3.0.