GitApplication · Git Scm
CVE-2019-1387
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGit before the listed versions contains a vulnerability in recursive clone operations where submodule names are insufficiently validated, allowing attackers to inject malicious paths or commands that execute during the clone process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitApplication
>= 2.14.0, < 2.14.6>= 2.15.0, < 2.15.4>= 2.16.0, < 2.16.6>= 2.17.0, < 2.17.3>= 2.18.0, < 2.18.2>= 2.19.0, < 2.19.3>= 2.20.0, < 2.20.2>= 2.22.0, < 2.22.2= 2.21.0= 2.23.0= 2.24.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Git versionRun 'git --version' on the command line and note the version number (e.g., output like 'git version 2.19.0')Affected if The version falls within any of these ranges: >= 2.14.0 and < 2.14.6; >= 2.15.0 and < 2.15.4; >= 2.16.0 and < 2.16.6; >= 2.17.0 and < 2.17.3; >= 2.18.0 and < 2.18.2; >= 2.19.0 and < 2.19.3; >= 2.20.0 and < 2.20.2; >= 2.22.0 and < 2.22.2; or is exactly 2.21.0, 2.23.0, or 2.24.0
-
Identify use of recursive clone with submodulesReview git operations performed, specifically look for use of 'git clone --recurse-submodules' or 'git submodule update --init --recursive' commands in your workflowsAffected if These recursive submodule operations are used with repositories or submodules from untrusted sources
-
Check for custom submodule configurationsExamine .gitmodules files in repositories you clone, looking for non-standard or unexpected submodule entriesAffected if Submodule URLs point to unexpected locations or paths that could be controlled by an attacker
You are affected if your installed Git version is one of the vulnerable versions listed AND you perform recursive clone operations on repositories containing submodules, particularly from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.14.62.15.42.16.6
Update Git installations to version 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, or v2.14.6 or later to patch the submodule validation flaw.
Fix this in Git
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data