Command execution via shell-interpolated branch name
Published Mar 27, 2023 · Updated Feb 24, 2025
Command injection in pullit before 1.4.0 allows remote attackers to execute arbitrary commands via a crafted GitHub branch name. The fetch method interpolates a pull request's unvalidated head.ref value into an execSync shell command that runs git fetch and git checkout. Execution requires a local user to run pullit and select the attacker's pull request, after which commands run with that user's privileges.
Summary
What happened
Command injection in pullit before 1.4.0 allows remote attackers to execute arbitrary commands via a crafted GitHub branch name. The fetch method interpolates a pull request's unvalidated head.ref value into an execSync shell command that runs git fetch and git checkout. Execution requires a local user to run pullit and select the attacker's pull request, after which commands run with that user's privileges.
The record
- CVE
- CVE-2018-25083
- Published
- Mar 27, 2023
- Updated
- Feb 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2023CVE publishedPublication date reported by the CVE source.
- Feb 24, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Snyk branch-name command-injection 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