{"id":103775,"date":"2022-04-13T03:37:00","date_gmt":"2022-04-13T01:37:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-git-2-35-2-s-ustraneniem-uyazvimostej"},"modified":"2022-04-13T03:37:00","modified_gmt":"2022-04-13T01:37:00","slug":"vypusk-git-2-35-2-s-ustraneniem-uyazvimostej","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-git-2-35-2-s-ustraneniem-uyazvimostej","title":{"rendered":"Release of Git 2.35.2 with Security Fixes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Corrective releases of the distributed version control system Git 2.35.2, 2.30.3, 2.31.2, 2.32.1, 2.33.2, and 2.34.2 have been published, addressing two vulnerabilities: <\/p>\n
\n
CVE-2022-24765 \u2014 a vulnerability identified in multi-user systems with shared directories allows an attacker to execute commands defined by another user. The attacker can create a directory named '.git' in locations that overlap with other users (for instance, in shared directories or those with temporary files) and place a configuration file '.git\/config' in it with handler settings triggered when specific git commands are executed (for example, the parameter core.fsmonitor can be used to facilitate code execution).\n
Handlers defined in '.git\/config' will be invoked with the permissions of another user if that user utilizes git in a directory located one level above the subdirectory '.git' created by the attacker. This invocation can also occur indirectly, for instance, when using code editors with git support, such as VS Code and Atom, or when applying extensions that trigger 'git status' (for example, Git Bash or posh-git). In Git version 2.35.2, the vulnerability has been mitigated by changes in how '.git' is searched in underlying directories (the '.git' directory is no longer considered if it belongs to another user). <\/p>\n
CVE-2022-24767 \u2014 a Windows-specific vulnerability that allows code execution with SYSTEM privileges during the uninstallation operation of Git for Windows. This issue occurs because the uninstaller runs from a temporary directory writable by system users. The attack is performed by placing replacement DLLs in the temporary directory, which will be loaded when the uninstaller is executed with SYSTEM privileges. <\/ul>\n