BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2019
CVE-2019-1387High confidence

Microsoft Corporation Git: security vulnerability

Microsoft Corporation · Git

8.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 4.43% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Microsoft Corporation Git and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

10 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitylibgit2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0.28.4-r0Alpine Security Database ↗Source updated 22 Oct 2026
Alpine v3.23v3.23 · maingitVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.24.1-r0Alpine Security Database ↗Source updated 23 Oct 2026
Alpine v3.22v3.22 · communitylibgit2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0.28.4-r0Alpine Security Database ↗Source updated 22 Oct 2026
Alpine v3.22v3.22 · maingitVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.24.1-r0Alpine Security Database ↗Source updated 23 Oct 2026
Alpine v3.21v3.21 · communitylibgit2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0.28.4-r0Alpine Security Database ↗Source updated 22 Oct 2026
Alpine v3.21v3.21 · maingitVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.24.1-r0Alpine Security Database ↗Source updated 23 Oct 2026
Debian trixietrixie · sourcegitVendor fix publishedDebian records a fixed source-package version for this release.1:2.24.0-2Debian Security Tracker ↗Source updated 23 Oct 2026
Debian bookwormbookworm · sourcegitVendor fix publishedDebian records a fixed source-package version for this release.1:2.24.0-2Debian Security Tracker ↗Source updated 23 Oct 2026
Debian forkyforky · sourcegitVendor fix publishedDebian records a fixed source-package version for this release.1:2.24.0-2Debian Security Tracker ↗Source updated 23 Oct 2026
Debian sidsid · sourcegitVendor fix publishedDebian records a fixed source-package version for this release.1:2.24.0-2Debian Security Tracker ↗Source updated 23 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2019-1387 · CSAF 2.0 · revision 32 · interimSUSE Product Security TeamCVE-2019-1387
65 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • git as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-core as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-cvs as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-daemon as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-doc as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-email as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-gui as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-svn as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git-web as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • gitk as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • git as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • git-core as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2019-9944

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code execution
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2022-1613git: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in git ausnutzen, um beliebigen Programmcode mit Benutzerrechten auszuführen oder um Daten zu manipulieren.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-650Multiples vulnérabilités dans les produits Juniper

.cve.org/CVERecord?id=CVE-2018-6954 Référence CVE CVE-2018-7489 https://www.cve.org/CVERecord?id=CVE-2018-7489 Référence CVE CVE-2018-8088 https://www.cve.org/CVERecord?id=CVE-2018-8088 Référence CVE CVE-2018-9251 https://www.cve.org/CVERecord?id=CVE-2018-9251 Référence CVE CVE-2019-0205 https://www.cve.org/CVERecord?id=CVE-2019-0205 Référence CVE CVE-2019-1349 https://www.cve.org/CVERecord?id=CVE-2019-1349 Référence CVE CVE-2019-1350 https://www.cve.org/CVERecord?id=CVE-2019-1350 Référence CVE CVE-2019-1352 https://www.cve.org/CVERecord?id=CVE-2019-1352 Référence CVE CVE-2019-1354 https://www.cve.org/CVERecord?id=CVE-2019-1354 Référence CVE CVE-2019-1387 https://www.cve.org/CVERecord?id=CVE-2019-1387 Référence CVE CVE-2019-14379 https://www.cve.org/CVERecord?id=CVE-2019-14379 Référence CVE CVE-2019-14540 https://www.cve.org/CVERecord?id=CVE-2019-14540 Référence CVE CVE-2019-14892 https://www.cve.org/CVERecord?id=CVE-2019-14892 Référence CVE CVE-2019-14893 https://www.cve.org/CVERecord?id=CVE-2019-14893 Référence CVE CVE-2019-16335 https://www.cve.org/CVERecord?id=CVE-2019-16335 Référence CVE CVE-2019-16942 https://www.cve.org/CVERecord?id=CVE-2019-16942 Référence CVE CVE-2019-16943 https://www.cve.org/CVERecord?id=CVE-2019-16943 Référence CVE CVE-2019-17267 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-351Multiples vulnérabilités dans les logiciels Juniper

elease-2011-L4?language=en_US Référence CVE CVE-2014-9471 https://www.cve.org/CVERecord?id=CVE-2014-9471 Référence CVE CVE-2015-8315 https://www.cve.org/CVERecord?id=CVE-2015-8315 Référence CVE CVE-2015-8391 https://www.cve.org/CVERecord?id=CVE-2015-8391 Référence CVE CVE-2018-1000654 https://www.cve.org/CVERecord?id=CVE-2018-1000654 Référence CVE CVE-2019-1349 https://www.cve.org/CVERecord?id=CVE-2019-1349 Référence CVE CVE-2019-1350 https://www.cve.org/CVERecord?id=CVE-2019-1350 Référence CVE CVE-2019-1352 https://www.cve.org/CVERecord?id=CVE-2019-1352 Référence CVE CVE-2019-1354 https://www.cve.org/CVERecord?id=CVE-2019-1354 Référence CVE CVE-2019-1387 https://www.cve.org/CVERecord?id=CVE-2019-1387 Référence CVE CVE-2020-35654 https://www.cve.org/CVERecord?id=CVE-2020-35654 Référence CVE CVE-2020-7774 https://www.cve.org/CVERecord?id=CVE-2020-7774 Référence CVE CVE-2021-23017 https://www.cve.org/CVERecord?id=CVE-2021-23017 Référence CVE CVE-2021-25289 https://www.cve.org/CVERecord?id=CVE-2021-25289 Référence CVE CVE-2021-26691 https://www.cve.org/CVERecord?id=CVE-2021-26691 Référence CVE CVE-2021-3156 https://www.cve.org/CVERecord?id=CVE-2021-3156 Référence CVE CVE-2021-31597 https://www.cve.org/CVERecord?id=CVE-2021-31597 Référence CVE CVE-2021-34552 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2019-AVI-627Multiples vulnérabilités dans les produits Microsoft

De multiples vulnérabilités ont été corrigées dans les produits Microsoft . Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une exécution de code à distance et une usurpation d'identité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-014249Microsoft Visual Studio におけるリモートでコードを実行される脆弱性

Microsoft Visual Studio には、Git for Visual Studio が入力を適切にサニタイズしない場合、リモートでコードを実行される脆弱性が存在します。 ベンダは、本脆弱性を「Git for Visual Studio のリモートでコードが実行される脆弱性」として公開しています。 本脆弱性は、CVE-2019-1349、CVE-2019-1350、CVE-2019-1352、CVE-2019-1387 とは異なる脆弱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-014245Microsoft Visual Studio におけるリモートでコードを実行される脆弱性

Microsoft Visual Studio には、Git for Visual Studio が入力を適切にサニタイズしない場合、リモートでコードが実行される脆弱性が存在します。 ベンダは、本脆弱性を「Git for Visual Studio のリモートでコードが実行される脆弱性」として公開しています。 本脆弱性は、CVE-2019-1350、 CVE-2019-1352、 CVE-2019-1354、 CVE-2019-1387 とは異なる脆弱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-014244Microsoft Visual Studio におけるリモートでコードを実行される脆弱性

Microsoft Visual Studio には、Git for Visual Studio が入力を適切にサニタイズしない場合、リモートでコードが実行される脆弱性が存在します。 ベンダは、本脆弱性を「Git for Visual Studio のリモートでコードが実行される脆弱性」として公開しています。 本脆弱性は、CVE-2019-1349、 CVE-2019-1352、 CVE-2019-1354、 CVE-2019-1387 とは異なる脆弱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-014242Microsoft Visual Studio におけるリモートでコードを実行される脆弱性

Microsoft Visual Studio には、Git for Visual Studio が入力を適切にサニタイズしない場合、リモートでコードが実行される脆弱性が存在します。 ベンダは、本脆弱性を「Git for Visual Studio のリモートでコードが実行される脆弱性」として公開しています。 本脆弱性は、CVE-2019-1349、 CVE-2019-1350、 CVE-2019-1354、 CVE-2019-1387 とは異なる脆弱性です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-013743Git における脆弱性

Git には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 18 Dec 2019 · Last source change 4 Nov 2025, 16:09 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2019-9944
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
  2. ENISA EUVD mappingEUVD-2019-9944 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2019-9944"}
    ENISA EUVD ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2019:4356; removed vendor advisory: access.redhat.com/RHSA-2020:0002; 7 further removals.
    Before
    vendor advisory: access.redhat.com/RHSA-2019:4356 · vendor advisory: access.redhat.com/RHSA-2020:0002 · vendor advisory: access.redhat.com/RHSA-2020:0124 · 6 more references
    After
    no authoritative guidance recorded
    CNA ↗
  4. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  5. CVSS scoreCVSS score changed from not recorded to 8.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    8.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)
    NIST NVD ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2019-9944↗SUSE Product Security Team security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2019-1387 · cve.blacktree.nl