CVE-2019-1387: High severity 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. 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
Event History
Frequently Asked Questions
What is the severity of CVE-2019-1387?
The severity of CVE-2019-1387 is high (8.8).
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.
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.
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.
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].