CVE-2019-1353: Critical severity git-scm Git vulnerability

Published Jan 24, 2020
·
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. When running Git in the Windows Subsystem for Linux (also known as "WSL") while accessing a working directory on a regular Windows drive, none of the NTFS protections were active.

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
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.21.0<2.21.1
git-scm Git>=2.22.0<2.22.2
git-scm Git>=2.23.0<2.23.1
git-scm Git>=2.24.0<2.24.1
openSUSE Leap=15.1
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 alpine/git to a version that resolves this vulnerability.

    Fixed in 2.22.2-r0
  3. Upgrade

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

    Fixed in 2.24.1-r0
  4. Upgrade

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

    Fixed in 2.15.4-r0
  5. Upgrade

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

    Fixed in 2.18.2-r0
  6. Upgrade

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

    Fixed in 2.20.2-r0
  7. Upgrade

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

    Fixed in 0.28.4-r0
  8. Upgrade

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

    Fixed in 0.28.4-r0
  9. 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·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is CVE-2019-1353?

CVE-2019-1353 is a vulnerability 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.

2

What is the severity of CVE-2019-1353?

CVE-2019-1353 has a severity rating of critical with a CVSS score of 9.8.

3

How does CVE-2019-1353 impact Git on Windows Subsystem for Linux (WSL)?

CVE-2019-1353 affects Git running on WSL while accessing a working directory on a regular Windows drive, bypassing NTFS protections.

4

How can I fix CVE-2019-1353?

To fix CVE-2019-1353, update Git to version 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 CVE-2019-1353?

You can find more information about CVE-2019-1353 on the official Git website and the Debian security tracker.

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