CVE-2018-17456: Critical severity git-scm Git vulnerability

Published Oct 5, 2018
·
Updated

A flaw was found in git which allows an attacker to execute arbitrary code by crafting a malicious .gitmodules file in a project cloned with --recurse-submodules.

References: https://bugzilla.novell.com/showbug.cgi?id=1110949 https://groups.google.com/forum/#!topic/git-packagers/fNLXf6LQC08

Other sources

Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code execution during processing of a recursive "git clone" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.

— Launchpad

Affected Software

31 affected componentsFixes available
redhat/git<2.14.5
2.14.5
redhat/git<2.15.3
2.15.3
redhat/git<2.16.5
2.16.5
redhat/git<2.17.2
2.17.2
redhat/git<2.18.1
2.18.1
redhat/git<2.19.1
2.19.1
git-scm Git>=2.14.0<2.14.5
git-scm Git>=2.15.0<2.15.3
git-scm Git>=2.16.0<2.16.5
git-scm Git>=2.17.0<2.17.2
git-scm Git>=2.18.0<2.18.1
git-scm Git>=2.19.0<2.19.1
redhat Ansible Tower=3.3
redhat Enterprise Linux=6.0
redhat Enterprise Linux=6.7
redhat Enterprise Linux=7.0
redhat Enterprise Linux=7.3
redhat Enterprise Linux=7.4
redhat Enterprise Linux=7.5
redhat Enterprise Linux=7.6
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Eus=7.6
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Workstation=7.0
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Debian Debian Linux=9.0
debian/git
1:2.30.2-1+deb11u21:2.30.2-1+deb11u51:2.39.5-0+deb12u31:2.39.5-0+deb12u21:2.47.3-0+deb13u11:2.51.0-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/git to a version that resolves this vulnerability.

    Fixed in 2.14.5
  2. Upgrade

    Upgrade redhat/git to a version that resolves this vulnerability.

    Fixed in 2.15.3
  3. Upgrade

    Upgrade redhat/git to a version that resolves this vulnerability.

    Fixed in 2.16.5
  4. Upgrade

    Upgrade redhat/git to a version that resolves this vulnerability.

    Fixed in 2.17.2
  5. Upgrade

    Upgrade redhat/git to a version that resolves this vulnerability.

    Fixed in 2.18.1
  6. Upgrade

    Upgrade redhat/git to a version that resolves this vulnerability.

    Fixed in 2.19.1
  7. Upgrade

    Upgrade debian/git to a version that resolves this vulnerability.

    Fixed in 1:2.30.2-1+deb11u2Fixed in 1:2.30.2-1+deb11u5Fixed in 1:2.39.5-0+deb12u3Fixed in 1:2.39.5-0+deb12u2Fixed in 1:2.47.3-0+deb13u1Fixed in 1:2.51.0-1
  8. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.14.5
  9. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.15.3
  10. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.16.5
  11. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.17.2
  12. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.18.1
  13. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.19.1

Event History

Oct 6, 2018
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:29 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is CVE-2018-17456?

CVE-2018-17456 is a vulnerability in Git that allows remote code execution during processing of a recursive "git clone" of a superproject if a .gitmodules file has a URL field beginning with a '-' character.

2

What is the severity of CVE-2018-17456?

The severity of CVE-2018-17456 is critical (9.8).

3

Which software versions are affected by CVE-2018-17456?

Git versions before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 are affected by CVE-2018-17456.

4

How can I fix CVE-2018-17456?

To fix CVE-2018-17456, you should update Git to version 2.14.5 or later.

5

Where can I find more information about CVE-2018-17456?

You can find more information about CVE-2018-17456 at the following references: [http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html](http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html), [http://packetstormsecurity.com/files/152173/Sourcetree-Git-Arbitrary-Code-Execution-URL-Handling.html](http://packetstormsecurity.com/files/152173/Sourcetree-Git-Arbitrary-Code-Execution-URL-Handling.html), [http://www.securityfocus.com/bid/105523](http://www.securityfocus.com/bid/105523).

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203