CVE-2019-1387: 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.
Noroxi assessment
Priority: Monitor (action score 36/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: 4.4% (FIRST EPSS); higher than 91.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 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
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.
- Published
- Dec 18, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.4% · 91th percentile
- CWE
- —
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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 |
|---|---|---|
| git-scm | git | cpe:2.3:a:git-scm:git |
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 Corporation Git
- Before v2.24.1, Before v2.23.1, Before v2.22.2, Before v2.21.1, Before v2.20.2, Before v2.19.3, Before v2.18.2, Before v2.17.3, Before v2.16.6, Before v2.15.4, Before v2.14.6affected
Affected versions · NVD (11)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- git-scm git2.14.0 and later · before 2.14.6
- git-scm git2.15.0 and later · before 2.15.4
- git-scm git2.16.0 and later · before 2.16.6
- git-scm git2.17.0 and later · before 2.17.3
- git-scm git2.18.0 and later · before 2.18.2
- git-scm git2.19.0 and later · before 2.19.3
- git-scm git2.20.0 and later · before 2.20.2
- git-scm git2.22.0 and later · before 2.22.2
- git-scm git2.21.0
- git-scm git2.23.0
- git-scm git2.24.0
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 | from 2.14.0 · before 2.22.2-r0 | 2.22.2-r0 |
| Alpine:v3.11 | git | from 2.14.0 · 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 | from 2.14.0 · before 2.15.4-r0 | 2.15.4-r0 |
| Alpine:v3.8 | git | from 2.14.0 · before 2.18.2-r0 | 2.18.2-r0 |
| Alpine:v3.9 | git | from 2.14.0 · 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:10 | git | before 1:2.20.1-2+deb10u9 | 1:2.20.1-2+deb10u9 |
| Debian:11 | git | before 1:2.30.2-1+deb11u3 | 1:2.30.2-1+deb11u3 |
| 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.26.1-lp151.4.9.1 | 2.26.1-lp151.4.9.1 |
| openSUSE:Leap 15.1 | git | before 2.16.4-lp151.4.3.1 | 2.16.4-lp151.4.3.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:7::client | emacs-git | before 0:1.8.3.1-21.el7_7 | 0:1.8.3.1-21.el7_7 |
| Red Hat:enterprise_linux:7::client | emacs-git-el | before 0:1.8.3.1-21.el7_7 | 0:1.8.3.1-21.el7_7 |
| Red Hat:enterprise_linux:7::client | git | before 0:1.8.3.1-21.el7_7 | 0:1.8.3.1-21.el7_7 |
| Red Hat:enterprise_linux:7::client | git-all | before 0:1.8.3.1-21.el7_7 | 0:1.8.3.1-21.el7_7 |
+75
Same product
git-scm: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows…68This week
- CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV63This week
- CVE-2021-21300malicious repositories can execute remote code while cloning60This week
Published before and after this one in the same product
- ← EarlierCVE-2018-1000021Feb 9, 2018 · GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up…20Monitor
- ← EarlierCVE-2019-19604Dec 10, 2019 · Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x…32Monitor
- Later →CVE-2019-1348Jan 24, 2020 · 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.13Monitor
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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-009 · Jan 8, 2020(Git Zafiyeti)
Not on record for this CVE: EPSS history · 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)
—
CVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (13 more)Show less
- lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html
- access.redhat.com/errata/RHSA-2019:4356
- access.redhat.com/errata/RHSA-2020:0002
- access.redhat.com/errata/RHSA-2020:0124
- access.redhat.com/errata/RHSA-2020:0228
- lists.debian.org/debian-lts-announce/2020/01/msg00019.html
- lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/N6UGTEOXWIYSM5KDZL74QD2GK6YQNQCP/
- lore.kernel.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/T/#u
- public-inbox.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/
- security.gentoo.org/glsa/202003-30
- security.gentoo.org/glsa/202003-42
- lists.debian.org/debian-lts-announce/2024/09/msg00009.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.