{"id":113130,"date":"2024-01-26T11:28:07","date_gmt":"2024-01-26T09:28:07","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/uyazvimost-v-gitlab-pozvolyayushhaya-zapisat-fajly-v-proizvolnyj-katalog-na-servere"},"modified":"2024-01-26T11:28:07","modified_gmt":"2024-01-26T09:28:07","slug":"uyazvimost-v-gitlab-pozvolyayushhaya-zapisat-fajly-v-proizvolnyj-katalog-na-servere","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/uyazvimost-v-gitlab-pozvolyayushhaya-zapisat-fajly-v-proizvolnyj-katalog-na-servere","title":{"rendered":"Vulnerability in GitLab allowing files to be written to arbitrary directories on the server","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Corrective updates for the collaborative development platform have been released \u2014 GitLab 16.8.1, 16.7.4, 16.6.6, and 16.5.8, addressing 5 vulnerabilities. One of the issues (CVE-2024-0402), which has been present since GitLab 16.0, has been assigned a critical severity level. This vulnerability allows an authenticated user to write files to any directory on the server, depending on the access permissions under which the GitLab web interface operates. <\/p>\n
The vulnerability is caused by an error in the implementation of the workspace creation function. The error occurs when parsing devfile parameters specified in an incorrect YAML format (the patch resolves the issue by converting YAML to JSON and checking for constructs valid in YAML but not allowed in JSON due to the use of certain Unicode characters). Detailed information about the vulnerability is expected to be disclosed 30 days after the release of the fix. The vulnerability was identified during an internal audit by one of GitLab's employees. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"