CVE-2017-1000117

Exp

A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any program that exists on the victim's machine being executed. Such a URL could be placed in the .gitmodules file of a malicious project, and an unsuspecting victim could be tricked into running "git clone --recurse-submodules" to trigger the vulnerability.

Published: 2017-10-04 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-1000117 is rated High Exploit Risk (90/100): CVSS High severity, with high exploitation likelihood (EPSS 77.82%, 100th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +7.58% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2017-1000117

EDB-ID Source Kind Published Link
42599 exploit_db edb 2017-08-31 Exploit-DB ↗

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

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 70.25% 77.82% +7.58%
2 2026-06-12 72.50% 70.25% -2.25%
3 2026-06-10 — 72.50% —

Full EPSS history (63 records total)

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

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:N/UI:R/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:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-1000117

OS Trackers for CVE-2017-1000117

vendor priority summary link
alpine — CVE-2017-1000117: 1 source package rows (git); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2017-1000117
debian not yet assigned CVE-2017-1000117 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-1000117
gentoo normal CVE-2017-1000117: 1 GLSA(s) (201709-10), 1 atom(s) (dev-vcs/git); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-1000117
redhat high — https://access.redhat.com/security/cve/CVE-2017-1000117
suse high CVE-2017-1000117 severity important: SUSE including 185 source package names (emacs-git-1.8.3.1-12.el7_4, emacs-git-el-1.8.3.1-12.el7_4, …), 317 product×package rows across 55 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (55 product lines)): Fixed 222, Known Not Affected 95. https://www.suse.com/security/cve/CVE-2017-1000117/
ubuntu medium CVE-2017-1000117 medium priority: Ubuntu including 1 source packages (git), 4 status rows across 4 suites (trusty, upstream, xenial, zesty): released 3, needs-triage 1. https://ubuntu.com/security/CVE-2017-1000117

Affected software / configurations for CVE-2017-1000117

Vendor Product Version Raw CPE
git-scm git <= 2.7.5 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git 2.8.0 cpe:2.3:a:git-scm:git:2.8.0:*:*:*:*:*:*:*
git-scm git 2.8.0 cpe:2.3:a:git-scm:git:2.8.0:rc0:*:*:*:*:*:*
git-scm git 2.8.0 cpe:2.3:a:git-scm:git:2.8.0:rc1:*:*:*:*:*:*
git-scm git 2.8.0 cpe:2.3:a:git-scm:git:2.8.0:rc2:*:*:*:*:*:*
git-scm git 2.8.0 cpe:2.3:a:git-scm:git:2.8.0:rc3:*:*:*:*:*:*
git-scm git 2.8.1 cpe:2.3:a:git-scm:git:2.8.1:*:*:*:*:*:*:*
git-scm git 2.8.2 cpe:2.3:a:git-scm:git:2.8.2:*:*:*:*:*:*:*
git-scm git 2.8.3 cpe:2.3:a:git-scm:git:2.8.3:*:*:*:*:*:*:*
git-scm git 2.8.4 cpe:2.3:a:git-scm:git:2.8.4:*:*:*:*:*:*:*
git-scm git 2.8.5 cpe:2.3:a:git-scm:git:2.8.5:*:*:*:*:*:*:*
git-scm git 2.9.0 cpe:2.3:a:git-scm:git:2.9.0:*:*:*:*:*:*:*
git-scm git 2.9.0 cpe:2.3:a:git-scm:git:2.9.0:rc0:*:*:*:*:*:*
git-scm git 2.9.0 cpe:2.3:a:git-scm:git:2.9.0:rc1:*:*:*:*:*:*
git-scm git 2.9.0 cpe:2.3:a:git-scm:git:2.9.0:rc2:*:*:*:*:*:*
git-scm git 2.9.1 cpe:2.3:a:git-scm:git:2.9.1:*:*:*:*:*:*:*
git-scm git 2.9.2 cpe:2.3:a:git-scm:git:2.9.2:*:*:*:*:*:*:*
git-scm git 2.9.3 cpe:2.3:a:git-scm:git:2.9.3:*:*:*:*:*:*:*
git-scm git 2.9.4 cpe:2.3:a:git-scm:git:2.9.4:*:*:*:*:*:*:*
git-scm git 2.10.0 cpe:2.3:a:git-scm:git:2.10.0:*:*:*:*:*:*:*
git-scm git 2.10.0 cpe:2.3:a:git-scm:git:2.10.0:rc0:*:*:*:*:*:*
git-scm git 2.10.0 cpe:2.3:a:git-scm:git:2.10.0:rc1:*:*:*:*:*:*
git-scm git 2.10.0 cpe:2.3:a:git-scm:git:2.10.0:rc2:*:*:*:*:*:*
git-scm git 2.10.1 cpe:2.3:a:git-scm:git:2.10.1:*:*:*:*:*:*:*
git-scm git 2.10.2 cpe:2.3:a:git-scm:git:2.10.2:*:*:*:*:*:*:*
git-scm git 2.10.3 cpe:2.3:a:git-scm:git:2.10.3:*:*:*:*:*:*:*
git-scm git 2.11.0 cpe:2.3:a:git-scm:git:2.11.0:*:*:*:*:*:*:*
git-scm git 2.11.0 cpe:2.3:a:git-scm:git:2.11.0:rc0:*:*:*:*:*:*
git-scm git 2.11.0 cpe:2.3:a:git-scm:git:2.11.0:rc1:*:*:*:*:*:*
git-scm git 2.11.0 cpe:2.3:a:git-scm:git:2.11.0:rc2:*:*:*:*:*:*
git-scm git 2.11.0 cpe:2.3:a:git-scm:git:2.11.0:rc3:*:*:*:*:*:*
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.12.0 cpe:2.3:a:git-scm:git:2.12.0:*:*:*:*:*:*:*
git-scm git 2.12.0 cpe:2.3:a:git-scm:git:2.12.0:rc0:*:*:*:*:*:*
git-scm git 2.12.0 cpe:2.3:a:git-scm:git:2.12.0:rc1:*:*:*:*:*:*
git-scm git 2.12.0 cpe:2.3:a:git-scm:git:2.12.0:rc2:*:*:*:*:*:*
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.13.0 cpe:2.3:a:git-scm:git:2.13.0:*:*:*:*:*:*:*
git-scm git 2.13.0 cpe:2.3:a:git-scm:git:2.13.0:rc0:*:*:*:*:*:*
git-scm git 2.13.0 cpe:2.3:a:git-scm:git:2.13.0:rc1:*:*:*:*:*:*
git-scm git 2.13.0 cpe:2.3:a:git-scm:git:2.13.0:rc2:*:*:*:*:*:*
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.14.0 cpe:2.3:a:git-scm:git:2.14.0:*:*:*:*:*:*:*
git-scm git 2.14.0 cpe:2.3:a:git-scm:git:2.14.0:rc0:*:*:*:*:*:*
git-scm git 2.14.0 cpe:2.3:a:git-scm:git:2.14.0:rc1:*:*:*:*:*:*

References for CVE-2017-1000117

cvelogic Threat Intelligence