CVE-2019-1387
HIGH
8.8
CVSS Score
Published: December 18, 2019 at 08:11 PM UTC
Updated: June 17, 2026 at 02:28 AM UTC
3 products affected across 3 vendorsGitGitGit for Windows
Using Git by Microsoft Corporation?
Get instant alerts when new vulnerabilities affect Git - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 4%
SSVC
No known exploit
Description
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
2.14.0 ≤ v < 2.14.62.15.0 ≤ v < 2.15.42.16.0 ≤ v < 2.16.62.17.0 ≤ v < 2.17.32.18.0 ≤ v < 2.18.22.19.0 ≤ v < 2.19.32.20.0 ≤ v < 2.20.22.22.0 ≤ v < 2.22.22.21.02.23.02.24.0
Affected range stops below 2.14.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.15.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.17.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.18.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.19.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.20.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.22.2, so it looks safe — our inference, not a vendor statement
v < 2,24.1v < 2.14.6v < 2.15.4v < 2.16.6v < 2.17.3v < 2.18.2v < 2.19.3v < 2.20.2v < 2.21.1v < 2.22.2v < 2.23.1
Affected range stops below 2,24.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.14.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.15.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.17.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.18.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.19.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.20.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.21.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.22.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.23.1, so it looks safe — our inference, not a vendor statement
v < 2.14.6v < 2.15.4v < 2.16.6v < 2.17.3v < 2.18.2v < 2.19.3v < 2.20.2v < 2.21.1v < 2.22.2v < 2.23.1v < 2.24.1
Affected range stops below 2.14.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.15.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.16.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.17.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.18.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.19.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.20.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.21.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.22.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.23.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.24.1, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (14)
Vendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00056.htmlVendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.htmlVendor AdvisoryThird Party Advisory
Source: [email protected]
https://access.redhat.com/errata/RHSA-2019:4356Vendor Advisoryx_refsource_REDHAT
Source: [email protected]
https://access.redhat.com/errata/RHSA-2020:0228SSVC — Action Prioritization
SSVCNo known exploitNot automatableTotal impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
- Attack Vector
- NETWORK
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- REQUIRED
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- HIGH
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
NVD-CWE-noinfo
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card