CVE-2024-32021
Assigner: GitHub_M
Published: 2024-05-14T19:15:28.534Z
State: PUBLISHED
title: Local Git clone may hardlink arbitrary user-readable files into the new repository's "objects/" directory
problemTypes: descriptions: cweId: CWE-547
description: CWE-547: Use of Hard-coded, Security-relevant Constants
type: CWE
metrics: cvssV3_1: attackComplexity: HIGH
attackVector: LOCAL
availabilityImpact: LOW
baseScore: 3.9
baseSeverity: LOW
confidentialityImpact: NONE
integrityImpact: LOW
privilegesRequired: LOW
scope: CHANGED
userInteraction: REQUIRED
vectorString: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L
version: 3.1
affected: vendor: git
product: git
versions: version: = 2.45.0
status: affected
version: = 2.44.0
status: affected
version: >= 2.43.0, < 2.43.4
status: affected
version: >= 2.42.0, < 2.42.2
status: affected
version: = 2.41.0
status: affected
version: >= 2.40.0, < 2.40.2
status: affected
version: < 2.39.4
status: affected
descriptions: value: 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.
source: advisory: GHSA-mvxm-9j2h-qjx7
discovery: UNKNOWN