CVE-2017-14867

Git 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.

Published: 2017-09-28 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-14867 is rated High Risk (74.6/100): CVSS High severity, with high exploitation likelihood (EPSS 36.00%, 98th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +29.47% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-14867

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 6.53% 36.00% +29.47%
2 2026-04-17 6.97% 6.53% -0.43%
3 2025-08-30 — 6.97% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-14867

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
9.0 2.0 HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.0 10.0 [email protected]

Weakness enumeration for CVE-2017-14867

OS Trackers for CVE-2017-14867

vendor priority summary link
debian not yet assigned CVE-2017-14867 not yet assigned priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-14867
redhat medium — https://access.redhat.com/security/cve/CVE-2017-14867
suse high CVE-2017-14867 severity important: SUSE including 169 source package names (git, git-1.7.12.4-0.18.6.1, …), 297 product×package rows across 52 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (52 product lines)): Fixed 202, Known Not Affected 95. https://www.suse.com/security/cve/CVE-2017-14867/
ubuntu medium CVE-2017-14867 medium priority: Ubuntu including 1 source packages (git), 4 status rows across 4 suites (trusty, upstream, xenial, zesty): released 4. https://ubuntu.com/security/CVE-2017-14867

Affected software / configurations for CVE-2017-14867

Vendor Product Version Raw CPE
git-scm git <= 2.10.4 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git 2.11.0 cpe:2.3:a:git-scm:git:2.11.0:*:*:*:*:*:*:*
git-scm git 2.11.1 cpe:2.3:a:git-scm:git:2.11.1:*:*:*:*:*:*:*
git-scm git 2.11.2 cpe:2.3:a:git-scm:git:2.11.2:*:*:*:*:*:*:*
git-scm git 2.11.3 cpe:2.3:a:git-scm:git:2.11.3:*:*:*:*:*:*:*
git-scm git 2.12.0 cpe:2.3:a:git-scm:git:2.12.0:*:*:*:*:*:*:*
git-scm git 2.12.1 cpe:2.3:a:git-scm:git:2.12.1:*:*:*:*:*:*:*
git-scm git 2.12.2 cpe:2.3:a:git-scm:git:2.12.2:*:*:*:*:*:*:*
git-scm git 2.12.3 cpe:2.3:a:git-scm:git:2.12.3:*:*:*:*:*:*:*
git-scm git 2.12.4 cpe:2.3:a:git-scm:git:2.12.4:*:*:*:*:*:*:*
git-scm git 2.13.0 cpe:2.3:a:git-scm:git:2.13.0:*:*:*:*:*:*:*
git-scm git 2.13.1 cpe:2.3:a:git-scm:git:2.13.1:*:*:*:*:*:*:*
git-scm git 2.13.2 cpe:2.3:a:git-scm:git:2.13.2:*:*:*:*:*:*:*
git-scm git 2.13.3 cpe:2.3:a:git-scm:git:2.13.3:*:*:*:*:*:*:*
git-scm git 2.13.4 cpe:2.3:a:git-scm:git:2.13.4:*:*:*:*:*:*:*
git-scm git 2.13.5 cpe:2.3:a:git-scm:git:2.13.5:*:*:*:*:*:*:*
git-scm git 2.14.0 cpe:2.3:a:git-scm:git:2.14.0:*:*:*:*:*:*:*
git-scm git 2.14.1 cpe:2.3:a:git-scm:git:2.14.1:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*

References for CVE-2017-14867

cvelogic Threat Intelligence