Skip to content
Noroxi
CVE-2019-1350· NVD / CVE Program· CNA microsoft

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E

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-1349, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jan 24, 2020
Updated
Jun 16, 2026
EPSS
25.7% · 98th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

43

Plan

Add it to your regular patch cycle.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
8 / 30 · 25.7%

Affected systems

VendorProduct
microsoftvisual studio 2017
microsoftvisual studio 2019

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

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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10gitbefore 2.22.2-r02.22.2-r0
Alpine:v3.11gitbefore 2.24.1-r02.24.1-r0
Alpine:v3.11libgit2before 0.28.4-r00.28.4-r0
Alpine:v3.7gitbefore 2.15.4-r02.15.4-r0
Alpine:v3.8gitbefore 2.18.2-r02.18.2-r0
Alpine:v3.9gitbefore 2.20.2-r02.20.2-r0
Debian:12gitbefore 1:2.24.0-21:2.24.0-2
openSUSE:Leap 15.1gitbefore 2.16.4-lp151.4.3.12.16.4-lp151.4.3.1
openSUSE:Leap 15.1gitbefore 2.26.1-lp151.4.9.12.26.1-lp151.4.9.1
openSUSE:Leap 15.1perl-Authen-SASLbefore 2.16-lp151.3.3.12.16-lp151.3.3.1
openSUSE:Leap 15.1perl-Net-SMTP-SSLbefore 1.04-lp151.3.3.11.04-lp151.3.3.1
openSUSE:Tumbleweedgitbefore 2.33.0-1.32.33.0-1.3
openSUSE:Tumbleweedlibgit2before 1.1.1-1.21.1.1-1.2
SUSE:HPE Helion OpenStack 8gitbefore 2.12.3-27.22.12.12.3-27.22.1
SUSE:Linux Enterprise Module for Basesystem 15gitbefore 2.16.4-3.17.22.16.4-3.17.2
SUSE:Linux Enterprise Module for Basesystem 15 SP1gitbefore 2.26.1-3.25.22.26.1-3.25.2
SUSE:Linux Enterprise Module for Development Tools 15perl-Authen-SASLbefore 2.16-1.3.12.16-1.3.1
SUSE:Linux Enterprise Module for Development Tools 15perl-Net-SMTP-SSLbefore 1.04-1.3.11.04-1.3.1

Other highest-scoring records for the same primary product.

  • CVE-2021-36952Visual Studio Remote Code Execution Vulnerability
    46Plan
  • CVE-2019-1349A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    45Plan
  • CVE-2019-1354A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    42Plan
  • CVE-2019-1352A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    42Plan
  • CVE-2019-0546A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ construc
    36Monitor
  • CVE-2025-21178Visual Studio Remote Code Execution Vulnerability
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:git2.22.2-r0 · Alpine:v3.10Package registry (OSV)
alpine:libgit20.28.4-r0 · Alpine:v3.11Package registry (OSV)
debian:git1:2.24.0-2 · Debian:12Package registry (OSV)
opensuse:git2.16.4-lp151.4.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:libgit21.1.1-1.2 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:perl-Authen-SASL2.16-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:perl-Net-SMTP-SSL1.04-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:git2.12.3-27.22.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:perl-Authen-SASL2.16-1.3.1 · SUSE:Linux Enterprise Module for Development Tools 15Package registry (OSV)
suse:perl-Net-SMTP-SSL1.04-1.3.1 · SUSE:Linux Enterprise Module for Development Tools 15Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records