Impact
The Git project recommends to avoid working in untrusted repositories, and instead to clone them first with git clone --no-local to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed.
In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004.
But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a .zip file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository.
Patches
The problem has been patched in the versions published on Tuesday, May 14th, 2024.
Workarounds
Avoid using Git in repositories that have been obtained via archives from untrusted sources.
References
peff Remediation developer
Impact
The Git project recommends to avoid working in untrusted repositories, and instead to clone them first with
git clone --no-localto obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed.In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004.
But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a
.zipfile containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository.Patches
The problem has been patched in the versions published on Tuesday, May 14th, 2024.
Workarounds
Avoid using Git in repositories that have been obtained via archives from untrusted sources.
References
git clone