CVE-2017-1000117
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 77.8% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 77.8% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 77.8% · EPSS, next 30 days
- Weakness
- CWE-601
- Record status
- Modified
Affected
- git-scm Git ≤ 2.7.5
- git-scm Git 2.8.0
- git-scm Git 2.8.1
- git-scm Git 2.8.2
- git-scm Git 2.8.3
- git-scm Git 2.8.4
- git-scm Git 2.8.5
- git-scm Git 2.9.0
Attack profile CVSS 3.0 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-1000117.md and follow it. Check whether this project is affected by CVE-2017-1000117. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://www.debian.org/security/2017/dsa-3934
- http://www.securityfocus.com/bid/100283
- http://www.securitytracker.com/id/1039131
- https://access.redhat.com/errata/RHSA-2017:2484
- https://access.redhat.com/errata/RHSA-2017:2485
- https://access.redhat.com/errata/RHSA-2017:2491
- https://access.redhat.com/errata/RHSA-2017:2674
- https://access.redhat.com/errata/RHSA-2017:2675
- https://security.gentoo.org/glsa/201709-10
- https://support.apple.com/HT208103
- https://www.exploit-db.com/exploits/42599/
- https://www.mail-archive.com/linux-kernel%40vger.kernel.org/msg1466490.html
- http://www.debian.org/security/2017/dsa-3934
- http://www.securityfocus.com/bid/100283
- http://www.securitytracker.com/id/1039131
- https://access.redhat.com/errata/RHSA-2017:2484
- https://access.redhat.com/errata/RHSA-2017:2485
- https://access.redhat.com/errata/RHSA-2017:2491
- https://access.redhat.com/errata/RHSA-2017:2674
- https://access.redhat.com/errata/RHSA-2017:2675
- https://security.gentoo.org/glsa/201709-10
- https://support.apple.com/HT208103
- https://www.exploit-db.com/exploits/42599/
- https://www.mail-archive.com/linux-kernel%40vger.kernel.org/msg1466490.html