8.8
CWE
601
Advisory Published
CVE Published
Updated

CVE-2017-1000117

First published: Thu Aug 10 2017(Updated: )

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.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/git<2.7.6
2.7.6
redhat/git<2.8.6
2.8.6
redhat/git<2.9.5
2.9.5
redhat/git<2.10.4
2.10.4
redhat/git<2.11.3
2.11.3
redhat/git<2.12.4
2.12.4
redhat/git<2.13.5
2.13.5
redhat/git<2.14.1
2.14.1
Git Git-shell<=2.7.5
Git Git-shell=2.8.0
Git Git-shell=2.8.0-rc0
Git Git-shell=2.8.0-rc1
Git Git-shell=2.8.0-rc2
Git Git-shell=2.8.0-rc3
Git Git-shell=2.8.1
Git Git-shell=2.8.2
Git Git-shell=2.8.3
Git Git-shell=2.8.4
Git Git-shell=2.8.5
Git Git-shell=2.9.0
Git Git-shell=2.9.0-rc0
Git Git-shell=2.9.0-rc1
Git Git-shell=2.9.0-rc2
Git Git-shell=2.9.1
Git Git-shell=2.9.2
Git Git-shell=2.9.3
Git Git-shell=2.9.4
Git Git-shell=2.10.0
Git Git-shell=2.10.0-rc0
Git Git-shell=2.10.0-rc1
Git Git-shell=2.10.0-rc2
Git Git-shell=2.10.1
Git Git-shell=2.10.2
Git Git-shell=2.10.3
Git Git-shell=2.11.0
Git Git-shell=2.11.0-rc0
Git Git-shell=2.11.0-rc1
Git Git-shell=2.11.0-rc2
Git Git-shell=2.11.0-rc3
Git Git-shell=2.11.1
Git Git-shell=2.11.2
Git Git-shell=2.12.0
Git Git-shell=2.12.0-rc0
Git Git-shell=2.12.0-rc1
Git Git-shell=2.12.0-rc2
Git Git-shell=2.12.1
Git Git-shell=2.12.2
Git Git-shell=2.12.3
Git Git-shell=2.13.0
Git Git-shell=2.13.0-rc0
Git Git-shell=2.13.0-rc1
Git Git-shell=2.13.0-rc2
Git Git-shell=2.13.1
Git Git-shell=2.13.2
Git Git-shell=2.13.3
Git Git-shell=2.13.4
Git Git-shell=2.14.0
Git Git-shell=2.14.0-rc0
Git Git-shell=2.14.0-rc1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2017-1000117?

    CVE-2017-1000117 is classified as a high severity vulnerability due to the potential for remote code execution.

  • How do I fix CVE-2017-1000117?

    You can fix CVE-2017-1000117 by upgrading to Git version 2.7.6 or later.

  • What type of vulnerability is CVE-2017-1000117?

    CVE-2017-1000117 is a remote code execution vulnerability.

  • Which software versions are affected by CVE-2017-1000117?

    CVE-2017-1000117 affects Git versions up to and including 2.7.5, and specific versions of 2.8.x and 2.9.x.

  • Can exploit of CVE-2017-1000117 lead to loss of data?

    Yes, the exploitation of CVE-2017-1000117 can potentially lead to data loss if an attacker executes malicious code on the victim's machine.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203