GitApplication · Git Scm
CVE-2017-14867
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 · uneditedGit before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support subcommands such as cvsserver, which allows attackers to execute arbitrary OS commands via shell metacharacters in a module name. The vulnerable code is reachable via git-shell even without CVS support.
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 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 contains unsafe Perl scripts supporting subcommands such as cvsserver. These scripts fail to properly sanitize module names, allowing attackers to inject shell metacharacters and execute arbitrary OS commands. The vulnerable code path is reachable through git-shell even when CVS support is not actively used.
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.10.4= 2.11.0= 2.11.1= 2.11.2= 2.11.3= 2.12.0= 2.12.1= 2.12.2= 2.12.3= 2.12.4= 2.13.0= 2.13.1
Debian LinuxOperating system
= 8.0= 9.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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` and note the version number (e.g., git version 2.12.3)Affected if Version is 2.10.4 or lower, or 2.11.0-2.11.3, or 2.12.0-2.12.4, or 2.13.0-2.13.1, or 2.14.0-2.14.1
-
Locate the cvsserver scriptRun `git --exec-path` to find the libexec directory, then check for the presence of git-cvsserver or cvsserver perl scripts in that directoryAffected if The cvsserver script exists in the Git libexec directory
-
Verify git-shell availabilityCheck if git-shell is present by running `which git-shell` or looking in the same exec-path directoryAffected if git-shell is installed and accessible on the system
-
Confirm version is in vulnerable rangeCompare your installed version against the affected list: <=2.10.4, 2.11.0-2.11.3, 2.12.0-2.12.4, 2.13.0-2.13.1Affected if Your version matches any of the affected versions AND the cvsserver script is present
You are affected if you have an installed Git version in the vulnerable list AND the cvsserver perl script exists in your Git installation, as the injection flaw can be triggered through git-shell even if CVS is not actively used.
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 dataUpgrade Git installations to version 2.10.5, 2.11.4, 2.12.5, 2.13.6, 2.14.2 or later. If immediate patching is not possible, disable or restrict access to git-shell and subcommand interfaces like cvsserver.
Fix this in Git
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14867 — 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-2017-14867 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