# CVE-2024-32465: Git's protections for cloning untrusted repositories can be bypassed > Attackers can bypass Git's safety protections when cloning untrusted repositories from archives, leading to arbitrary code execution via malicious hooks. - **Severity:** High 7.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 May 2024 - **Updated:** 4 Nov 2025 - **Also known as:** ALPINE-CVE-2024-32465, AZL-42046, AZL-43053, BELL-CVE-2024-32465, BIT-git-2024-32465, CLEANSTART-2026-JB28862, CLSA-2024-1728056367, CLSA-2025-1737156361, DEBIAN-CVE-2024-32465, GHSA-vm9j-46j9-qvq4, UBUNTU-CVE-2024-32465 ## What is CVE-2024-32465? CVE-2024-32465 is a high-severity code injection vulnerability in Debian Debian Linux, published on 14 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2024-32465? 1 open source package ship an affected version, including git. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `git` | Bitnami | All versions | 2.39.4, 2.40.2, 2.41.1, 2.42.2, 2.43.4, 2.44.1, 2.45.1 | Products: Debian Debian Linux, Fedoraproject Fedora, Git-Scm Git. ## How do I fix CVE-2024-32465? Upgrade git to a fixed version for your release line: 2.39.4, 2.40.2, 2.41.1 or 2.42.2. ## Is CVE-2024-32465 being exploited? There is no known exploitation of CVE-2024-32465 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32465 and fix it if it is affected. What it is: CVE-2024-32465 is a high-severity code injection vulnerability in Debian Debian Linux, published on 14 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-32465 in the wild and no public exploit code. Affected packages and fixed versions: - git (Bitnami): affected all versions; fixed in 2.39.4, 2.40.2, 2.41.1, 2.42.2, 2.43.4, 2.44.1, 2.45.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32465/ (Markdown: https://insights.sbomify.com/CVE-2024-32465/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32465 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32465 - OSV: https://osv.dev/vulnerability/CVE-2024-32465 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32465/ Summaries are generated and may contain mistakes; the official description above is the record.