First published: Tue May 14 2024(Updated: )
An attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Microsoft Visual Studio 2019 (includes 16.0 - 16.10) | =16.11 | |
Microsoft Visual Studio 2022 | =17.8 | |
Microsoft Visual Studio 2017 (includes 15.0 - 15.8) | =15.9 | |
Microsoft Visual Studio 2022 | =17.6 | |
redhat/git | <2.45.1 | 2.45.1 |
redhat/git | <2.44.1 | 2.44.1 |
redhat/git | <2.43.4 | 2.43.4 |
redhat/git | <2.42.2 | 2.42.2 |
redhat/git | <2.41.1 | 2.41.1 |
redhat/git | <2.40.2 | 2.40.2 |
redhat/git | <2.39.4 | 2.39.4 |
debian/git | <=1:2.30.2-1+deb11u2 | 1:2.30.2-1+deb11u4 1:2.39.5-0+deb12u1 1:2.39.5-0+deb12u2 1:2.47.2-0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-32004 is classified as a high severity vulnerability due to the potential for arbitrary code execution when a manipulated repository is cloned.
To fix CVE-2024-32004, upgrade to Git versions 2.45.2 or later, or apply patches as specified in your software vendor's release notes.
CVE-2024-32004 affects Git versions prior to 2.45.1, including 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Yes, third-party tools that leverage the affected versions of Git may be at risk of exploitation via CVE-2024-32004.
Yes, Microsoft Visual Studio versions that include vulnerable Git components are affected by CVE-2024-32004 and should be updated.