CVE-2024-32020
Reported by github_m · Published May 14, 2024
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. 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.
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-subtree | 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-instaweb | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-email | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-core-doc | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-core | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
| git-p4 | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-svn | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
| perl-Git-SVN | Amazon Linux | 2.40.1-1.amzn2023.0.3, 2.40.1-1.amzn2.0.3 |
| git-cvs | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
| git-daemon | Amazon Linux | 2.40.1-1.amzn2.0.3 |
| git-all | Amazon Linux | 2.40.1-1.amzn2023.0.3 |
5 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-subtree | 0 |
| amazon:2 | git-credential-libsecret | 0 |
| amazon:2 | git-instaweb | 0 |
| amazon:2023 | git-email | 0 |
| amazon:2 | git-email | 0 |
| amazon:2023 | git-core-doc | 0 |
| amazon:2023 | git-core | 0 |
| amazon:2023 | git-p4 | 0 |
| amazon:2023 | git-svn | 0 |
| amazon:2 | git-core-doc | 0 |
| amazon:2023 | git-credential-libsecret | 0 |
| amazon:2023 | perl-Git-SVN | 0 |
| amazon:2023 | git-cvs | 0 |
| amazon:2 | git-p4 | 0 |
| amazon:2 | git-daemon | 0 |
| amazon:2023 | git-all | 0 |
| amazon:2 | git-gui | 0 |
| amazon:2 | perl-Git | 0 |
| amazon:2 | git | 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 (11 in total, the first dated here)
- Feb 13, 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-32020
vulnetix vdb fixes CVE-2024-32020
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-32020/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-5rfh-556j-fhgj x_refsource_CONFIRM
- https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d x_refsource_MISC
- https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703 x_refsource_MISC