CVE-2024-32020: low-severity vulnerability in git
Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
No sign of exploitation. No public exploitation artifact known so far.
When cloning a Git repository from another user on the same disk, Git may create hardlinks to files instead of copies. This allows the original owner to secretly modify those files later, potentially corrupting your repository.
Local Git clone operations create hardlinks to source repository objects when both repositories reside on the same filesystem. An untrusted source repository owner can subsequently modify hardlinked objects in the target repository without authorization, compromising repository integrity. Mitigation requires Git version 2.45.1 or later, which avoids hardlinking when source and target owners differ.
In the same product, most dangerous first.