Local code execution via unquoted branch names
Published Jan 13, 2021 · Updated Aug 3, 2024
Code injection in git-big-picture before 1.0.0 allows local users to execute commands through a crafted Git branch name. The ref parser passed git for-each-ref output containing attacker-controlled ref names to Python eval without language-safe quoting. Execution occurs when a user runs git-big-picture against a repository containing the malicious branch, and the command runs with that user's privileges.
Summary
What happened
Code injection in git-big-picture before 1.0.0 allows local users to execute commands through a crafted Git branch name. The ref parser passed git for-each-ref output containing attacker-controlled ref names to Python eval without language-safe quoting. Execution occurs when a user runs git-big-picture against a repository containing the malicious branch, and the command runs with that user's privileges.
The record
- CVE
- CVE-2021-3028
- Published
- Jan 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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.
Public exploit references
- Upstream crafted-branch reproducerproof 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