Code execution via project-local Git binary
Published Jun 22, 2020 · Updated Aug 4, 2024
Code execution in GitLab for VS Code 2.2.0 and earlier allows attackers to run commands when a user opens a crafted repository. The extension invokes Git through execa 1.0.0 with preferLocal enabled, causing executable resolution to search the opened project before trusted locations. A user must open the attacker-controlled repository and trigger a Git operation, after which a planted Git executable runs with the editor user's privileges.
Summary
What happened
Code execution in GitLab for VS Code 2.2.0 and earlier allows attackers to run commands when a user opens a crafted repository. The extension invokes Git through execa 1.0.0 with preferLocal enabled, causing executable resolution to search the opened project before trusted locations. A user must open the attacker-controlled repository and trigger a Git operation, after which a planted Git executable runs with the editor user's privileges.
The record
- CVE
- CVE-2020-13279
- Published
- Jun 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab for VS Code
- Classifications
- CWE-427, T1574.007
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=<=2.2.0
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
No public exploit references are available in this record.
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