low
3.9
CWE
281
Advisory Published
CVE Published
Updated

CVE-2024-32020: Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at will

First published: Tue May 14 2024(Updated: )

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.

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
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+deb11u4
1:2.39.5-0+deb12u2
1:2.47.2-0.1
1:2.49.0-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-32020?

    CVE-2024-32020 is classified as a moderate severity vulnerability affecting certain versions of Git.

  • How do I fix CVE-2024-32020?

    To fix CVE-2024-32020, update Git to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, or 2.39.4, depending on your distribution.

  • What systems are impacted by CVE-2024-32020?

    CVE-2024-32020 impacts local clones of Git repositories when the source and target repositories are on the same disk.

  • Is CVE-2024-32020 specific to certain Git installations?

    Yes, CVE-2024-32020 specifically affects Git installations prior to versions 2.45.1, 2.44.1, and several others listed in the vulnerability details.

  • What happens if I don't address CVE-2024-32020?

    Failing to address CVE-2024-32020 could result in unintended file linking and potential data integrity issues in your Git repositories.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203