Git objects/ hard-coded, security-relevant constants

Summaryinfo

A vulnerability has been found in Git and classified as problematic. This affects an unknown part of the file objects/. The manipulation leads to use of hard-coded, security-relevant constants. This vulnerability is referenced as CVE-2024-32021. The attack can only be performed from a local environment. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Git (the affected version unknown). It has been rated as problematic. This issue affects an unknown part of the file objects/. The manipulation with an unknown input leads to a use of hard-coded, security-relevant constants vulnerability. Using CWE to declare the problem leads to CWE-547. The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change. Impacted is integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-32021 since 04/09/2024. The exploitation is known to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 214460 (SUSE SLES12 Security Update : git (SUSE-SU-2025:0197-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (214460). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Versioning Software

Name

• Git

License

• open-source

Website

• Product: https://github.com/git/git/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion