low
3.9
CWE
547
Advisory Published
CVE Published
Updated

CVE-2024-32021: Local Git clone may hardlink arbitrary user-readable files into the new repository's "objects/" directory

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, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. 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-32021?

    CVE-2024-32021 is classified with a moderate severity level due to its potential to create hardlinks to user-readable files.

  • How do I fix CVE-2024-32021?

    To mitigate CVE-2024-32021, upgrade Git to versions 2.45.1 or newer, or ensure you are using a version not affected by the vulnerability.

  • Which versions of Git are affected by CVE-2024-32021?

    CVE-2024-32021 affects Git versions prior to 2.45.1, including 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

  • Who is affected by CVE-2024-32021?

    Anyone cloning Git repositories containing symlinks on their filesystem using affected versions of Git is at risk from CVE-2024-32021.

  • Is there a workaround for CVE-2024-32021?

    The best workaround for CVE-2024-32021 is to avoid using affected versions of Git until you can upgrade to a fixed version.

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