Skip to content
Noroxi
NVD / CVE Program· CNA microsoft

CVE-2019-1351: A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vul

Noroxi assessment

Priority: Monitor (action score 33/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 8.7% (FIRST EPSS); higher than 95.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. 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 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. 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 tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual Studio Tampering Vulnerability'.

HighCVSS 7.5 · v3.1—Proof of concept Fix available
Published
Jan 24, 2020
Updated
Jun 16, 2026
EPSS
8.7% · 95th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 8.7%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-1351

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for microsoft records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
microsoftvisual studio 2017
microsoftvisual studio 2019
opensuseleap

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
  • opensuse leap15.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

Same product

microsoft: all records

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-1350A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    43Plan

Published before and after this one in the same product

  • ← EarlierCVE-2019-1211Aug 14, 2019 · Git for Visual Studio Elevation of Privilege Vulnerability
    29Monitor
  • ← 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-1352Jan 24, 2020 · A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code E
    42Plan

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

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02020-07-13

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.

  1. Published
  2. First PoC+170 d
  3. TodayOct 29, 2026+2469 d
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.

Credits

All researchers

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-706 · Use of Incorrectly-Resolved Name or Reference

CVSS vector

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

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records