Vulnerabilities · 2019 · Git-scm
CVE-2019-1353
Git-scm Git vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Git, Leap. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Git-scm Git runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- lists.opensuse.org/opensuse-security-announce/2020-01/msg00056.html · Third Party Advisory
- lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html
- lore.kernel.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/T/#u
- public-inbox.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/
- security.gentoo.org/glsa/202003-30
- nvd.nist.gov/vuln/detail/CVE-2019-1353
- cve.org/CVERecord?id=CVE-2019-1353
More vulnerabilities in Git-scm products
CVE-2025-48384CVE-2024-32465CVE-2024-32021CVE-2024-32020CVE-2024-32004CVE-2023-29007CVE-2023-25652CVE-2023-23946All 41
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.