CVE-2024-32002: Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution
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.
Credit
Affected Software
Remediation
Event History
Frequently Asked Questions
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.
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.
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.
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.
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.