CVE-2024-32004: Git vulnerable to Remote Code Execution while cloning special-crafted local repositories

Published 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.

Other sources

GitHub: CVE-2024-32004 Remote Code Execution while cloning special-crafted local repositories

— Microsoft

Affected Software

33 affected componentsFixes available
Microsoft Visual Studio 2019 (includes 16.0 - 16.10)=16.11
Patch available
Microsoft Visual Studio 2017 (includes 15.0 - 15.8)=15.9
Patch available
Microsoft Visual Studio 2022=17.9
Patch available
Microsoft Visual Studio 2022=17.4
Patch available
git-scm Git<2.39.4
git-scm Git>=2.40.0<2.40.2
git-scm Git>=2.42.0<2.42.2
git-scm Git>=2.43.0<2.43.4
git-scm Git=2.41.0
git-scm Git=2.44.0
git-scm Git=2.45.0
Fedoraproject Fedora=40
Debian Debian Linux=10.0
Debian Debian Linux=11.0
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
alpine/git>=2.40.0<2.39.5-r0
2.39.5-r0
alpine/git>=2.40.0<2.40.3-r0
2.40.3-r0
alpine/git>=2.40.0<2.43.4-r0
2.43.4-r0
alpine/git>=2.40.0<2.45.1-r0
2.45.1-r0
alpine/git>=2.40.0<2.45.1-r0
2.45.1-r0
alpine/git>=2.40.0<2.45.1-r0
2.45.1-r0
alpine/git>=2.40.0<2.45.1-r0
2.45.1-r0
alpine/git>=2.40.0<2.45.1-r0
2.45.1-r0
debian/git<1:2.39.5-0+deb12u1
1:2.39.5-0+deb12u1
debian/git<1:2.45.1-1
1:2.45.1-1
debian/git<1:2.45.1-1
1:2.45.1-1
debian/git
1:2.39.5-0+deb12u31:2.39.5-0+deb12u21:2.47.3-0+deb13u11:2.53.0-11:2.55.0-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 2.45.1
  2. Upgrade

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

    Fixed in 2.44.1
  3. Upgrade

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

    Fixed in 2.43.4
  4. Upgrade

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

    Fixed in 2.42.2
  5. Upgrade

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

    Fixed in 2.41.1
  6. Upgrade

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

    Fixed in 2.40.2
  7. Upgrade

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

    Fixed in 2.39.4
  8. Upgrade

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

    Fixed in 2.39.5-r0
  9. Upgrade

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

    Fixed in 2.40.3-r0
  10. Upgrade

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

    Fixed in 2.43.4-r0
  11. Upgrade

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

    Fixed in 2.45.1-r0
  12. Upgrade

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

    Fixed in 1:2.39.5-0+deb12u1
  13. Upgrade

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

    Fixed in 1:2.45.1-1
  14. Upgrade

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

    Fixed in 1:2.39.5-0+deb12u3Fixed in 1:2.39.5-0+deb12u2Fixed in 1:2.47.3-0+deb13u1Fixed in 1:2.53.0-1Fixed in 1:2.55.0-1
  15. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.45.1
  16. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.44.1
  17. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.43.4
  18. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.42.2
  19. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.41.1
  20. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.40.2
  21. Upgrade

    Upgrade Git to a version that resolves this vulnerability.

    Fixed in 2.39.4
  22. Compensating control

    Avoid cloning repositories from untrusted sources (workaround for CVE-2024-32004).

Event History

May 14, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·06:46 PM
Data Sourced
via MITRE·06:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·07:15 PM
DescriptionSeverityAffected Software
Data Sourced
via Red Hat·11:27 PM
DescriptionSeverityAffected Software
May 19, 2024
Exploit Published
via GitHub·01:57 PM

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-32004?

CVE-2024-32004 is classified as a high severity vulnerability due to the potential for arbitrary code execution when a manipulated repository is cloned.

2

How do I fix CVE-2024-32004?

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.

3

Which versions of Git are vulnerable to CVE-2024-32004?

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.

4

Can third-party tools be affected by CVE-2024-32004?

Yes, third-party tools that leverage the affected versions of Git may be at risk of exploitation via CVE-2024-32004.

5

Is Visual Studio impacted by CVE-2024-32004?

Yes, Microsoft Visual Studio versions that include vulnerable Git components are affected by CVE-2024-32004 and should be updated.

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