GitHub Action tj-actions/verify-changed-files is vulnerable to command injection in output filenames
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 17.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The `tj-actions/verify-changed-files` action allows for command injection in changed filenames, allowing an attacker to execute arbitrary code and potentially leak secrets. The `verify-changed-files` workflow returns the list of files changed within a workflow execution. This could potentially allow filenames that contain special characters such as `;` which can be used by an attacker to take over the GitHub Runner if the output value is used in a raw fashion (thus being directly replaced before execution) inside a `run` block. By running custom commands, an attacker may be able to steal secrets such as `GITHUB_TOKEN` if triggered on other events than `pull_request`. This has been patched in versions 17 and 17.0.0 by enabling `safe_output` by default and returning filename paths escaping special characters for bash environments.
Timeline
- CVE published
- Record last updated
Affected versions
- tj-actions verify-changed-files
fixed in 17.0.0