CVE-2019-1349: Input Validation

Published Dec 9, 2019
·
Updated

A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1350, CVE-2019-1352, CVE-2019-1354, CVE-2019-1387.

Other sources

When using submodule paths that refer to the same file system entity (e.g. using the NTFS Alternate Data Streams attack mentioned in CVE-2019-1352 where files would be written to the .git/ directory using a synonymous directory name), it was possible to "squat" on the git~1 shortname on NTFS drives, opening attacks via git~2. This also affects Git when run as a Linux application inside the Windows Subsystem for Linux.

References:

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

— Red Hat

Affected Software

49 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
Microsoft Visual Studio 2017>=15.0<15.9.18
Microsoft Visual Studio 2019>=16.0<16.4.1
alpine/git<2.22.2-r0
2.22.2-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.24.1-r0
2.24.1-r0
alpine/git<2.15.4-r0
2.15.4-r0
alpine/git<2.18.2-r0
2.18.2-r0
alpine/git<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

Jan 24, 2020
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-1349?

CVE-2019-1349 is classified as a remote code execution vulnerability.

2

How do I fix CVE-2019-1349?

To fix CVE-2019-1349, update Git to the recommended versions listed in the advisory.

3

Which software is affected by CVE-2019-1349?

CVE-2019-1349 affects Git for Visual Studio and certain versions of Git on Debian and Red Hat.

4

Can CVE-2019-1349 allow an attacker to execute commands remotely?

Yes, CVE-2019-1349 can allow an attacker to execute arbitrary commands on the vulnerable system.

5

What are the potential impacts of CVE-2019-1349?

The potential impacts of CVE-2019-1349 include unauthorized access and control over the affected systems.

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