CVE-2024-32465

Git's protections for cloning untrusted repositories can be bypassed

Published May 14, 2024 CVSS 3.1 · 7.4 High EPSS 1.0% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-3844-1 git security update
Debian DLA Debian DLA DLA-3867-1 git security update
Debian DSA Debian DSA DSA-5769-1 git security update
EUVD EUVD EUVD-2024-30280 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.
Ubuntu USN Ubuntu USN USN-6793-1 Git vulnerabilities
Ubuntu USN Ubuntu USN USN-7023-1 Git vulnerabilities
History
Type Values Removed Values Added
First Time appeared Debian
Debian debian Linux
Fedoraproject
Fedoraproject fedora
Git-scm
Git-scm git
CPEs cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
cpe:2.3:a:git-scm:git:2.41.0:*:*:*:*:*:*:*
cpe:2.3:a:git-scm:git:2.44.0:*:*:*:*:*:*:*
cpe:2.3:a:git-scm:git:2.45.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*
Vendors & Products Debian
Debian debian Linux
Fedoraproject
Fedoraproject fedora
Git-scm
Git-scm git
Type Values Removed Values Added
First Time appeared Git
Git git
CPEs cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
Vendors & Products Git
Git git
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 4, 2025, 4:12 PM
Reserved
Apr 12, 2024, 7:41 PM
Status
Analyzed
Published
May 14, 2024, 8:15 PM
Modified
Jun 17, 2026, 7:29 AM
Severity
Moderate
Public date
May 14, 2024, 12:00 AM