{"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\/nl\/blog\/news\/vypusk-git-2-35-2-s-ustraneniem-uyazvimostej","title":{"rendered":"Git-release 2.35.2 met kwetsbaarheid oplossen","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Correcties zijn gepubliceerd voor de gedistribueerde broncodebeheersysteem Git 2.35.2, 2.30.3, 2.31.2, 2.32.1, 2.33.2 en 2.34.2, waarin twee kwetsbaarheden zijn opgelost: <\/p>\n
\n
CVE-2022-24765 \u2014 in multi-user systems with shared directories, an attack vector has been identified that allows for the execution of commands defined by other users. An attacker can create a directory '.git' in locations that overlap with other users (for example, in shared directories or temporary file folders) and place a configuration file '.git\/config' in it with settings for handlers invoked when certain git commands are executed (for example, the core.fsmonitor parameter can be used to execute code).\n
Handlers defined in '.git\/config' will be invoked with the permissions of another user if that user uses git in a directory located one level above the subdirectory '.git' created by the attacker. The invocation can also occur indirectly, for example, when using code editors with git support, such as VS Code and Atom, or when using extensions that trigger 'git status' (such as Git Bash or posh-git). In Git version 2.35.2, the vulnerability has been mitigated through changes in the logic for searching '.git' in lower-level directories (the '.git' directory is now ignored if it belongs to another user). <\/p>\n
CVE-2022-24767 \u2014 a platform-specific vulnerability for Windows that allows for code execution with SYSTEM privileges when uninstalling the Git for Windows program. The issue arises because the uninstaller runs in a temporary directory that is writable by system users. The attack is carried out by placing replacement DLLs in the temporary directory, which will be loaded when the uninstaller is executed with SYSTEM privileges. <\/ul>\n