CVE-2024-32465
Git's protections for cloning untrusted repositories can be bypassed
Reported by github_m · Published May 14, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| git-core-doc | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
| git-credential-libsecret | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-svn | Amazon Linux | 2.40.1-1.amzn2.0.3 |
| git-all | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| perl-Git-SVN | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
| git-core | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| perl-Git | Amazon Linux | 2.40.1-1.amzn2.0.3 |
| git-gui | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
| git | Chainguard | 2.45.1-r0 |
| git | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-subtree | Amazon Linux | 2.40.1-1.amzn2.0.3 |
| gitweb | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
9 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| git | git | = 2.45.0, = 2.44.0, >= 2.43.0, < 2.43.4 |
| amazon:2023 | git-core-doc | 0 |
| amazon:2023 | git-credential-libsecret | 0 |
| amazon:2 | git-svn | 0 |
| amazon:2 | git-all | 0 |
| amazon:2023 | perl-Git-SVN | 0 |
| amazon:2 | git-core | 0 |
| amazon:2 | perl-Git | 0 |
| amazon:2023 | git-gui | 0 |
| chainguard | git | 0 |
| amazon:2 | git | 0 |
| amazon:2 | git-subtree | 0 |
| amazon:2023 | git-all | 0 |
| amazon:2023 | gitweb | 0 |
| alpine | git | 0, 0, 0 |
| amazon:2 | git-credential-libsecret | 0 |
| amazon:2023 | git-instaweb | 0 |
| amazon:2023 | git-cvs | 0 |
| wolfi | git | 0 |
| amazon:2023 | git-email | 0 |
…and 20 more
Timeline
- May 14, 2024 CVE Published
- May 15, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (12 in total, the first dated here)
- Nov 4, 2025 CVE Updated
- Jan 12, 2026 Security Advisory (13 in total, the first dated here)
- Sep 11, 2026 Distribution Patch (12 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-32465
vulnetix vdb fixes CVE-2024-32465
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-32465/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://github.com/git/git/security/advisories/GHSA-vm9j-46j9-qvq4 x_refsource_CONFIRM
- https://github.com/git/git/commit/7b70e9efb18c2cc3f219af399bd384c5801ba1d7 x_refsource_MISC
- https://git-scm.com/docs/git#_security x_refsource_MISC
- https://git-scm.com/docs/git-clone x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html advisory