CVE-2019-1349: A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code…
Noroxi assessment
Priority: Plan (action score 46/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 36% (FIRST EPSS); higher than 98.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: git (Alpine:v3.10) 2.22.2-r0; git (Alpine:v3.11) 2.24.1-r0; libgit2 (Alpine:v3.11) 0.28.4-r0.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to git (Alpine:v3.10) 2.22.2-r0; git (Alpine:v3.11) 2.24.1-r0; libgit2 (Alpine:v3.11) 0.28.4-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.
- Published
- Jan 24, 2020
- Updated
- Jun 16, 2026
- EPSS
- 36.0% · 98th percentile
- CWE
- CWE-20
Report tools
Action score
46
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 11 / 30 · 36.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | visual studio 2017 | cpe:2.3:a:microsoft:visual_studio_2017 |
| microsoft | visual studio 2019 | cpe:2.3:a:microsoft:visual_studio_2019 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft Visual Studio 2017
- 15.0affected
Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.1 - 15.8)
- unspecifiedaffected
Microsoft Microsoft Visual Studio 2019
- 16.0affected
Microsoft Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3)
- unspecifiedaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft visual studio 201715.0 and later · before 15.9.18
- microsoft visual studio 201916.0 and later · before 16.4.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | git | before 2.22.2-r0 | 2.22.2-r0 |
| Alpine:v3.11 | git | before 2.24.1-r0 | 2.24.1-r0 |
| Alpine:v3.11 | libgit2 | before 0.28.4-r0 | 0.28.4-r0 |
| Alpine:v3.13 | libgit2-1.0 | before 0.28.4-r0 | 0.28.4-r0 |
| Alpine:v3.15 | libgit2-1.1 | before 0.28.4-r0 | 0.28.4-r0 |
| Alpine:v3.7 | git | before 2.15.4-r0 | 2.15.4-r0 |
| Alpine:v3.8 | git | before 2.18.2-r0 | 2.18.2-r0 |
| Alpine:v3.9 | git | before 2.20.2-r0 | 2.20.2-r0 |
| Debian:10 | git | before 1:2.20.1-2+deb10u1 | 1:2.20.1-2+deb10u1 |
| Debian:12 | git | before 1:2.24.0-2 | 1:2.24.0-2 |
| Debian:8 | git | before 1:2.1.4-2.1+deb8u8 | 1:2.1.4-2.1+deb8u8 |
| Debian:9 | git | before 1:2.11.0-3+deb9u5 | 1:2.11.0-3+deb9u5 |
| openSUSE:Leap 15.1 | git | before 2.16.4-lp151.4.3.1 | 2.16.4-lp151.4.3.1 |
| openSUSE:Leap 15.1 | git | before 2.26.1-lp151.4.9.1 | 2.26.1-lp151.4.9.1 |
| openSUSE:Leap 15.1 | perl-Authen-SASL | before 2.16-lp151.3.3.1 | 2.16-lp151.3.3.1 |
| openSUSE:Leap 15.1 | perl-Net-SMTP-SSL | before 1.04-lp151.3.3.1 | 1.04-lp151.3.3.1 |
| openSUSE:Tumbleweed | git | before 2.33.0-1.3 | 2.33.0-1.3 |
| openSUSE:Tumbleweed | libgit2 | before 1.1.1-1.2 | 1.1.1-1.2 |
| Red Hat:enterprise_linux:8::appstream | git | before 0:2.18.2-1.el8_1 | 0:2.18.2-1.el8_1 |
| Red Hat:enterprise_linux:8::appstream | git-all | before 0:2.18.2-1.el8_1 | 0:2.18.2-1.el8_1 |
| Red Hat:enterprise_linux:8::appstream | git-core | before 0:2.18.2-1.el8_1 | 0:2.18.2-1.el8_1 |
| Red Hat:enterprise_linux:8::appstream | git-core-debuginfo | before 0:2.18.2-1.el8_1 | 0:2.18.2-1.el8_1 |
| Red Hat:enterprise_linux:8::appstream | git-core-doc | before 0:2.18.2-1.el8_1 | 0:2.18.2-1.el8_1 |
| Red Hat:enterprise_linux:8::appstream | git-daemon | before 0:2.18.2-1.el8_1 | 0:2.18.2-1.el8_1 |
+54
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-36952Visual Studio Remote Code Execution Vulnerability46Plan
- CVE-2019-1352A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code…43Plan
- CVE-2019-1350A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code…43Plan
Published before and after this one in the same product
- ← EarlierCVE-2019-1211Aug 14, 2019 · Git for Visual Studio Elevation of Privilege Vulnerability29Monitor
- ← EarlierCVE-2019-1425Nov 12, 2019 · An elevation of privilege vulnerability exists when Visual Studio fails to properly validate hardlinks while extracting archived files, aka…27Monitor
- Later →CVE-2019-1351Jan 24, 2020 · A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering…33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:git | 2.22.2-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:libgit2 | 0.28.4-r0 · Alpine:v3.11 | Package registry (OSV) |
| alpine:libgit2-1.0 | 0.28.4-r0 · Alpine:v3.13 | Package registry (OSV) |
| alpine:libgit2-1.1 | 0.28.4-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:git | 1:2.24.0-2 · Debian:12 | Package registry (OSV) |
| opensuse:git | 2.16.4-lp151.4.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:libgit2 | 1.1.1-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:perl-Authen-SASL | 2.16-lp151.3.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:perl-Net-SMTP-SSL | 1.04-lp151.3.3.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:git | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-all | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-core | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-core-debuginfo | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-core-doc | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-daemon | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-daemon-debuginfo | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-debuginfo | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-debugsource | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-email | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-gui | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:git-instaweb | 0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| suse:git | 2.12.3-27.22.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:perl-Authen-SASL | 2.16-1.3.1 · SUSE:Linux Enterprise Module for Development Tools 15 | Package registry (OSV) |
| suse:perl-Net-SMTP-SSL | 1.04-1.3.1 · SUSE:Linux Enterprise Module for Development Tools 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-061 · Jan 27, 2020(Visual Studio Güvenlik Güncellemesi)
- TR-20-009 · Jan 8, 2020(Git Zafiyeti)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.