CVE-2024-32002: Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution

Published May 14, 2024
·
Updated

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.

Other sources

Git. This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.

— Apple

GitHub: CVE-2024-32002 Recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution

— Microsoft

Repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed.

— Red Hat

Credit

CVE-2024-32002, Mickey Jin@@patch1t, Guilherme Rambo(Best Buddy Apps), Alexander Heinrich, SEEMOO, DistriNet, KU Leuven@@vanhoefm, TU Darmstadt@@Sn0wfreeze, Mathy Vanhoef, Wojciech Regula(SecuRing)

Affected Software

20 affected componentsFixes available
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
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
Apple Xcode<16
16
Git git<2.39.4
Git git>=2.40.0<2.40.2
Git git>=2.42.0<2.42.2
Git git>=2.43.0<2.43.4
Git git=2.41.0
Git git=2.44.0
Git git=2.45.0
debian/git<=1:2.30.2-1+deb11u2
1:2.30.2-1+deb11u41:2.39.5-0+deb12u21:2.47.2-0.11:2.49.0-1
Microsoft Visual Studio 2022=17.9
Patch available
Microsoft Visual Studio 2022=17.4
Patch available

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apple Xcode to a version that resolves this vulnerability.

    Fixed in 16
  2. Upgrade

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

    Fixed in 1:2.30.2-1+deb11u4Fixed in 1:2.39.5-0+deb12u2Fixed in 1:2.47.2-0.1Fixed in 1:2.49.0-1
  3. Upgrade

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

    Fixed in 2.45.1
  4. Upgrade

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

    Fixed in 2.44.1
  5. Upgrade

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

    Fixed in 2.43.4
  6. Upgrade

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

    Fixed in 2.42.2
  7. Upgrade

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

    Fixed in 2.41.1
  8. Upgrade

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

    Fixed in 2.40.2
  9. Upgrade

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

    Fixed in 2.39.4
  10. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.45.1
  11. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.44.1
  12. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.43.4
  13. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.42.2
  14. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.41.1
  15. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.40.2
  16. Upgrade

    Upgrade git to a version that resolves this vulnerability.

    Fixed in 2.39.4
  17. Configuration

    Disable symbolic link support in Git (e.g., set `git config --global core.symlinks false`).

    Git core.symlinks = false

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:40 PM
Data Sourced
via MITRE·06:40 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·11:10 PM
DescriptionSeverityAffected Software
Jun 29, 2024
Data Sourced
via Launchpad·04:51 PM
Description
Sep 21, 2024
Data Sourced
via Ubuntu·05:04 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-32002?

CVE-2024-32002 is classified as a medium severity vulnerability that could potentially lead to unauthorized file writing in Git repositories.

2

How do I fix CVE-2024-32002?

To fix CVE-2024-32002, update your Git installation to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, or 2.39.4 or higher.

3

Which software is affected by CVE-2024-32002?

CVE-2024-32002 affects various versions of Git prior to 2.45.1 as well as certain Microsoft Visual Studio and Apple Xcode versions.

4

What exploit does CVE-2024-32002 allow?

CVE-2024-32002 allows crafted Git repositories with submodules to write files to unexpected locations, compromising the integrity of the file system.

5

Are there any known exploits for CVE-2024-32002?

As of now, there are no public exploits confirmed for CVE-2024-32002, but users are encouraged to apply updates promptly.

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