Skip to content
Noroxi
NVD / CVE Program· CNA microsoft

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.

HighCVSS 8.8 · v3.1—No exploit Fix available

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

JSON

Action score

36

Monitor

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.

Follow CVE-2019-1387

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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
git-scmgit

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

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.10gitfrom 2.14.0 · before 2.22.2-r02.22.2-r0
Alpine:v3.11gitfrom 2.14.0 · before 2.24.1-r02.24.1-r0
Alpine:v3.11libgit2before 0.28.4-r00.28.4-r0
Alpine:v3.13libgit2-1.0before 0.28.4-r00.28.4-r0
Alpine:v3.15libgit2-1.1before 0.28.4-r00.28.4-r0
Alpine:v3.7gitfrom 2.14.0 · before 2.15.4-r02.15.4-r0
Alpine:v3.8gitfrom 2.14.0 · before 2.18.2-r02.18.2-r0
Alpine:v3.9gitfrom 2.14.0 · before 2.20.2-r02.20.2-r0
Debian:10gitbefore 1:2.20.1-2+deb10u11:2.20.1-2+deb10u1
Debian:10gitbefore 1:2.20.1-2+deb10u91:2.20.1-2+deb10u9
Debian:11gitbefore 1:2.30.2-1+deb11u31:2.30.2-1+deb11u3
Debian:12gitbefore 1:2.24.0-21:2.24.0-2
Debian:8gitbefore 1:2.1.4-2.1+deb8u81:2.1.4-2.1+deb8u8
Debian:9gitbefore 1:2.11.0-3+deb9u51:2.11.0-3+deb9u5
openSUSE:Leap 15.1gitbefore 2.26.1-lp151.4.9.12.26.1-lp151.4.9.1
openSUSE:Leap 15.1gitbefore 2.16.4-lp151.4.3.12.16.4-lp151.4.3.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
Red Hat:enterprise_linux:7::clientemacs-gitbefore 0:1.8.3.1-21.el7_70:1.8.3.1-21.el7_7
Red Hat:enterprise_linux:7::clientemacs-git-elbefore 0:1.8.3.1-21.el7_70:1.8.3.1-21.el7_7
Red Hat:enterprise_linux:7::clientgitbefore 0:1.8.3.1-21.el7_70:1.8.3.1-21.el7_7
Red Hat:enterprise_linux:7::clientgit-allbefore 0:1.8.3.1-21.el7_70:1.8.3.1-21.el7_7

+75

Other 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 quotingKEV
    63This week
  • CVE-2021-21300malicious repositories can execute remote code while cloning
    60This 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 / packageFixed versionSource
alpine:git2.22.2-r0 · Alpine:v3.10Package registry (OSV)
alpine:libgit20.28.4-r0 · Alpine:v3.11Package registry (OSV)
alpine:libgit2-1.00.28.4-r0 · Alpine:v3.13Package registry (OSV)
alpine:libgit2-1.10.28.4-r0 · Alpine:v3.15Package 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)
red hat:git0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-all0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-core0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-core-debuginfo0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-core-doc0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-daemon0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-daemon-debuginfo0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-debuginfo0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-debugsource0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-email0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-gui0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:git-instaweb0:2.18.2-1.el8_1 · Red Hat:enterprise_linux:8::appstreamPackage 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.

National notice (Türkiye Cybersecurity Directorate / USOM)

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

All national notices →

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.

References

All records