Home > Cyber News > CVE-2022-2884: Critical GitLab Vulnerability Enables Remote Code Execution

CVE-2022-2884: Critical GitLab Vulnerability Enables Remote Code Execution

CVE-2022-2884 gitlab vulnerability

GitLab revealed a critical vulnerability for branches 15.1, 15.2, and 15.3 of its community and enterprise editions. The vulnerability, identified as CVE-2022-2884 and rated 9.9 on the CVSS scale, could enable a threat actor to carry out remote command execution via Github Import.

Gitlab Versions Affected by CVE-2022-2884

All versions starting from 15.3 before 15.3.1are affected, Gitlab said. The vulnerability allows an authenticated user to achieve remote code execution by exploiting the Import from GitHub API endpoint. “This is a Critical severity issue (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, 9.9),” the company added.

The CVE-2022-2884 vulnerability has been reported by a researcher known as yvvdwf through GitLab’s HackerOne bug bounty program.

Workaround against CVE-2022-2884 Available

The company has also provided workaround tricks against the vulnerability for users who are unable to upgrade their installations right away.

First, you need to disable GitHub Import by logging in as an administrator and following these steps:

  • Click “Menu” -> “Admin”.
  • Click “Settings” -> “General”.
  • Expand the “Visibility and access controls” tab.
  • Under “Import sources” disable the “GitHub” option.
  • Click “Save changes”.

Then, the workaround should be verified by performing the following instructions:

  • In a browser window, login as any user.
  • Click “+” on the top bar.
  • Click “New project/repository”.
  • Click “Import project”.
  • Verify that “GitHub” does not appear as an import option.

In June, GitLab fixed another highly critical vulnerability that could lead to account takeover.

Tracked as CVE-2022-1680 and rated 9.9 out of 10 on the CVSS scale, the flaw affected all versions of GitLab Enterprise Edition from 11.10 before 14.9.5, all versions starting from 14.10 before 14.10.4, and all versions starting from 15.0 before 15.0.1. The issue was discovered internally by a member of the team.

Milena Dimitrova

An inspired writer and content manager who has been with SensorsTechForum since the project started. A professional with 10+ years of experience in creating engaging content. Focused on user privacy and malware development, she strongly believes in a world where cybersecurity plays a central role. If common sense makes no sense, she will be there to take notes. Those notes may later turn into articles! Follow Milena @Milenyim

More Posts

Follow Me:

Leave a Comment

Your email address will not be published. Required fields are marked *

This website uses cookies to improve user experience. By using our website you consent to all cookies in accordance with our Privacy Policy.
I Agree