CVE-2024-32465: Git's protections for cloning untrusted repositories can be bypassed

Published May 14, 2024
·
Updated

Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it 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. 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. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.

Other sources

Git's protections for cloning untrusted repositories can be bypassed

Microsoft

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.

Red Hat

Affected Software

23 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
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
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
Microsoft cbl2 git 2.33.8-2
Microsoft cbl2 git 2.33.8-2
Microsoft azl3 git 2.42.0-2
Microsoft azl3 git 2.45.2-1
Microsoft cbl2 git 2.39.4-1

Event History

May 14, 2024
CVE Published
via MITRE·07:18 PM
Data Sourced
via MITRE·07:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyAffected Software
May 17, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Jun 29, 2024
Data Sourced
via Launchpad·04:51 PM
Description
Sep 21, 2024
Data Sourced
via Ubuntu·05:04 PM
RemedyDescriptionSeverityAffected Software
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-32465?

CVE-2024-32465 is considered a moderate severity vulnerability affecting Git.

2

How do I fix CVE-2024-32465?

To fix CVE-2024-32465, upgrade Git to version 2.45.1 or later.

3

What software is affected by CVE-2024-32465?

CVE-2024-32465 affects multiple versions of the Git package, specifically versions prior to 2.45.1.

4

What could happen if I do not mitigate CVE-2024-32465?

If CVE-2024-32465 is not mitigated, you may expose your system to security risks from untrusted repositories.

5

Is CVE-2024-32465 a local or remote vulnerability?

CVE-2024-32465 is primarily a local vulnerability, as it deals with untrusted repositories that are cloned locally.

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