CVE-2019-1387: High severity git-scm Git vulnerability

Published Dec 9, 2019
·
Updated

An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.

Other sources

Recursive clones are currently affected by a vulnerability that is caused by too-lax validation of submodule names, allowing very targeted attacks via remote code execution in recursive clones.

References:

https://kernel.googlesource.com/pub/scm/git/git/+/refs/tags/v2.24.1/Documentation/RelNotes/2.14.6.txt

— Red Hat

Affected Software

58 affected componentsFixes available
debian/git
1:2.20.1-2+deb10u31:2.20.1-2+deb10u81:2.30.2-1+deb11u21:2.39.2-1.11:2.42.0-1
redhat/git<2.24.1
2.24.1
redhat/git<2.23.1
2.23.1
redhat/git<2.21.1
2.21.1
redhat/git<2.20.2
2.20.2
redhat/git<2.19.3
2.19.3
redhat/git<2.18.2
2.18.2
redhat/git<2.17.3
2.17.3
redhat/git<2.16.6
2.16.6
redhat/git<2.15.4
2.15.4
redhat/git<2.14.6
2.14.6
git-scm Git>=2.14.0<2.14.6
git-scm Git>=2.15.0<2.15.4
git-scm Git>=2.16.0<2.16.6
git-scm Git>=2.17.0<2.17.3
git-scm Git>=2.18.0<2.18.2
git-scm Git>=2.19.0<2.19.3
git-scm Git>=2.20.0<2.20.2
git-scm Git>=2.22.0<2.22.2
git-scm Git=2.21.0
git-scm Git=2.23.0
git-scm Git=2.24.0
alpine/git>=2.14.0<2.22.2-r0
2.22.2-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.24.1-r0
2.24.1-r0
alpine/git>=2.14.0<2.15.4-r0
2.15.4-r0
alpine/git>=2.14.0<2.18.2-r0
2.18.2-r0
alpine/git>=2.14.0<2.20.2-r0
2.20.2-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2<0.28.4-r0
0.28.4-r0
alpine/libgit2-1.0<0.28.4-r0
0.28.4-r0
alpine/libgit2-1.0<0.28.4-r0
0.28.4-r0
alpine/libgit2-1.1<0.28.4-r0
0.28.4-r0
alpine/libgit2-1.1<0.28.4-r0
0.28.4-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 1:2.20.1-2+deb10u3Fixed in 1:2.20.1-2+deb10u8Fixed in 1:2.30.2-1+deb11u2Fixed in 1:2.39.2-1.1Fixed in 1:2.42.0-1
  2. Upgrade

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

    Fixed in 2.24.1
  3. Upgrade

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

    Fixed in 2.23.1
  4. Upgrade

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

    Fixed in 2.22.2
  5. Upgrade

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

    Fixed in 2.21.1
  6. Upgrade

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

    Fixed in 2.20.2
  7. Upgrade

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

    Fixed in 2.19.3
  8. Upgrade

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

    Fixed in 2.18.2
  9. Upgrade

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

    Fixed in 2.17.3
  10. Upgrade

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

    Fixed in 2.16.6
  11. Upgrade

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

    Fixed in 2.15.4
  12. Upgrade

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

    Fixed in 2.14.6
  13. Upgrade

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

    Fixed in 2.22.2-r0
  14. Upgrade

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

    Fixed in 2.24.1-r0
  15. Upgrade

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

    Fixed in 2.15.4-r0
  16. Upgrade

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

    Fixed in 2.18.2-r0
  17. Upgrade

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

    Fixed in 2.20.2-r0
  18. Upgrade

    Upgrade alpine/libgit2 to a version that resolves this vulnerability.

    Fixed in 0.28.4-r0
  19. Upgrade

    Upgrade alpine/libgit2-1.0 to a version that resolves this vulnerability.

    Fixed in 0.28.4-r0
  20. Upgrade

    Upgrade alpine/libgit2-1.1 to a version that resolves this vulnerability.

    Fixed in 0.28.4-r0

Event History

Dec 18, 2019
CVE Published
via MITRE·08:11 PM
Data Sourced
via MITRE·08:11 PM
DescriptionWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-1387?

The severity of CVE-2019-1387 is high (8.8).

2

How does the vulnerability CVE-2019-1387 affect Git?

The vulnerability CVE-2019-1387 affects Git versions before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6.

3

What is the vulnerability CVE-2019-1387?

The vulnerability CVE-2019-1387 is caused by too-lax validation of submodule names in Git, allowing targeted attacks via remote code execution.

4

How can I fix the vulnerability CVE-2019-1387?

To fix the vulnerability CVE-2019-1387, users should update Git to versions v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, or v2.14.6.

5

Where can I find more information about the vulnerability CVE-2019-1387?

More information about the vulnerability CVE-2019-1387 can be found at the following references: [link1], [link2], [link3].

Company

Resources

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