Command execution via interpolated branch name
Published Dec 4, 2023 · Updated Aug 2, 2024
Code injection in tj-actions Branch Names before 7.0.7 allows remote attackers to execute commands through a crafted pull request branch name. The action.yml run step expands github.event.pull_request.head.ref or github.head_ref directly into Bash source instead of passing it through an environment variable. A repository workflow must invoke the action on attacker-controlled pull request data; successful exploitation can expose secrets or misuse token permissions.
Summary
What happened
Code injection in tj-actions Branch Names before 7.0.7 allows remote attackers to execute commands through a crafted pull request branch name. The action.yml run step expands github.event.pull_request.head.ref or github.head_ref directly into Bash source instead of passing it through an environment variable. A repository workflow must invoke the action on attacker-controlled pull request data; successful exploitation can expose secrets or misuse token permissions.
The record
- CVE
- CVE-2023-49291
- Published
- Dec 4, 2023
- Updated
- Aug 2, 2024
- Vendor
- tj-actions
- Product
- Branch Names
- Classifications
- CWE-94, T1059.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=< 7.0.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 branch-name command-injection payloadproof 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