Runner code execution via unescaped filename output
Published Dec 27, 2023 · Updated Sep 25, 2024
Command injection in tj-actions changed-files before 41.0.0 allows remote authenticated users to execute code through crafted filenames. The action emits changed-file paths while escaping only quotation marks, so shell metacharacters reach a raw workflow run block and are interpreted by Bash. Exploitation requires control of a committed or pull-request filename and an approved workflow that directly interpolates the affected output; successful commands run with the GitHub runner's permissions and can read accessible secrets.
Summary
What happened
Command injection in tj-actions changed-files before 41.0.0 allows remote authenticated users to execute code through crafted filenames. The action emits changed-file paths while escaping only quotation marks, so shell metacharacters reach a raw workflow run block and are interpreted by Bash. Exploitation requires control of a committed or pull-request filename and an approved workflow that directly interpolates the affected output; successful commands run with the GitHub runner's permissions and can read accessible secrets.
The record
- CVE
- CVE-2023-51664
- Published
- Dec 27, 2023
- Updated
- Sep 25, 2024
- Vendor
- tj-actions
- Product
- changed-files
- Classifications
- CWE-77, CWE-74, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 41.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted filename workflow proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo