{"id":115816,"date":"2024-05-16T02:59:27","date_gmt":"2024-05-16T00:59:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/pyat-uyazvimostej-v-git-sredi-kotoryh-odna-kriticheskaya-i-dve-opasnye"},"modified":"2024-05-16T02:59:27","modified_gmt":"2024-05-16T00:59:27","slug":"pyat-uyazvimostej-v-git-sredi-kotoryh-odna-kriticheskaya-i-dve-opasnye","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/pyat-uyazvimostej-v-git-sredi-kotoryh-odna-kriticheskaya-i-dve-opasnye","title":{"rendered":"Five vulnerabilities in Git, including one critical and two serious ones.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Corrective releases for the distributed source control system Git 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4 have been published, addressing five vulnerabilities. The most severe vulnerability (CVE-2024-32002), classified as critical, allows for remote code execution when using the command 'git clone' to clone a repository controlled by an attacker. <\/p>\n
The vulnerability manifests only in case-sensitive file systems that support symbolic links, such as those typically used in Windows and macOS. Exploitation occurs by creating a submodule directory and a symbolic link that differ only in case, which allows for file writes to the .git\/ directory instead of the submodule's working directory. By gaining write access to .git\/, an attacker can override hook calls via .git\/hooks and achieve arbitrary code execution during the 'git clone' operation. <\/p>\n
Other vulnerabilities: <\/p>\n
\n
CVE-2024-32004 \u2014 in a multi-user system, an attacker can prepare a specially crafted local repository that executes code upon cloning. Specifically, the attacker can create a local repository that appears as a partial clone missing a specific object. Cloning this repository will result in code execution with the privileges of the user performing the cloning operation.\n
CVE-2024-32465 \u2014 cloning from zip archives containing a complete git repository that includes hooks in the .git\/ directory will lead to the execution of those hooks.\n
CVE-2024-32020 \u2014 creating local clones of a repository on the same disk in a multi-user system allows other users to modify files that use hard links.\n
CVE-2024-32021 \u2014 cloning a local repository with symbolic links can be used to create hard links to arbitrary files in the objects\/ directory. <\/ul>\n
In addition to addressing vulnerabilities in new versions, several changes have been proposed aimed at enhancing protection against vulnerabilities that lead to remote code execution and manipulate symbolic links during cloning. For instance, Git now issues a warning when symbolic links are present in the .git\/ directory. Paths to submodules may now only contain real directories. In cases where symbolic links and directories intersect, directories are processed. During the execution of \"git clone,\" safeguards against triggering hooks during cloning have been implemented, and checks for the core.hooksPath parameter have been strengthened. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"