# CVE-2019-1387: Command injection in Git > Attackers can achieve remote code execution via targeted attacks on recursive clones due to lax submodule name validation in Git. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 18 Dec 2019 - **Updated:** 4 Nov 2025 - **Also known as:** ALPINE-CVE-2019-1387, CLEANSTART-2026-LI11422, DEBIAN-CVE-2019-1387, GHSA-9mhc-h3vf-83fw, RHSA-2020:0124, UBUNTU-CVE-2019-1387 ## What is CVE-2019-1387? CVE-2019-1387 is a high-severity command injection vulnerability in Microsoft Corporation Git, published on 18 Dec 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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. ## Which versions are affected by CVE-2019-1387? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `emacs-git` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `emacs-git-el` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-all` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-bzr` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-cvs` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-daemon` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-email` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-gnome-keyring` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-gui` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-hg` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-instaweb` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-p4` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `git-svn` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `gitk` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `gitweb` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `perl-Git` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `perl-Git-SVN` | Red Hat:enterprise_linux:7::client | All versions | 0:1.8.3.1-21.el7_7 | | `emacs-git` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `emacs-git-el` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-all` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-bzr` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-cvs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-daemon` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-email` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-gnome-keyring` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-gui` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-hg` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-instaweb` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-p4` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `git-svn` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `gitk` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `gitweb` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `perl-Git` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `perl-Git-SVN` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.8.3.1-21.el7_7 | | `emacs-git` | Red Hat:enterprise_linux:7::server | All versions | 0:1.8.3.1-21.el7_7 | | `emacs-git-el` | Red Hat:enterprise_linux:7::server | All versions | 0:1.8.3.1-21.el7_7 | Products: Git-Scm Git. ## How do I fix CVE-2019-1387? Upgrade to a fixed version. ## Is CVE-2019-1387 being exploited? There is no known exploitation of CVE-2019-1387 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft Corporation Git - [CVE-2022-23521](https://insights.sbomify.com/CVE-2022-23521/): gitattributes parsing integer overflow in git (critical 9.8) - [CVE-2022-41903](https://insights.sbomify.com/CVE-2022-41903/): Integer overflow in `git archive`, `git log --format` leading to RCE in git (critical 9.8) - [CVE-2019-1353](https://insights.sbomify.com/CVE-2019-1353/): Security feature bypass in Git (critical 9.8) - [CVE-2016-2315](https://insights.sbomify.com/CVE-2016-2315/): Memory corruption in n/a (critical 9.8) - [CVE-2016-2324](https://insights.sbomify.com/CVE-2016-2324/): Integer overflow in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1387 and fix it if it is affected. What it is: CVE-2019-1387 is a high-severity command injection vulnerability in Microsoft Corporation Git, published on 18 Dec 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-1387 in the wild and no public exploit code. Affected product: Microsoft Corporation Git. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-1387/ (Markdown: https://insights.sbomify.com/CVE-2019-1387/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1387 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1387 - OSV: https://osv.dev/vulnerability/CVE-2019-1387 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1387/ Summaries are generated and may contain mistakes; the official description above is the record.