CVE-2023-6955: Workspaces able to be created under different root namespace
A missing authorization check vulnerability exists in GitLab Remote Development affecting all versions prior to 16.5.6, 16.6 prior to 16.6.4 and 16.7 prior to 16.7.2. This condition allows an attacker to create a workspace in one group that is associated with an agent from another group.
Other sources
An improper access control vulnerability exists in GitLab Workspaces affecting all versions prior to 16.5.6, 16.6 prior to 16.6.4 and 16.7 prior to 16.7.2. This condition allows an attacker to create a workspace in one group that is associated with an agent from another group. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N, 6.6). It is now mitigated in the latest release and is assigned CVE-2023-6955.
— GitLab
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.6.4Fixed in 16.7.2 - Upgrade
Upgrade
GitLab Remote Development / GitLab Workspacesto a version that resolves this vulnerability.Fixed in 16.5.6 - Upgrade
Upgrade
GitLab Remote Development / GitLab Workspacesto a version that resolves this vulnerability.Fixed in 16.6.4 - Upgrade
Upgrade
GitLab Remote Development / GitLab Workspacesto a version that resolves this vulnerability.Fixed in 16.7.2
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2023-6955?
CVE-2023-6955 is considered a significant vulnerability due to the missing authorization check allowing unauthorized workspace creation.
How do I fix CVE-2023-6955?
To fix CVE-2023-6955, upgrade to GitLab version 16.5.6, 16.6.4 or 16.7.2 or later.
Which versions of GitLab are affected by CVE-2023-6955?
CVE-2023-6955 affects all versions prior to 16.5.6, 16.6 before 16.6.4, and 16.7 before 16.7.2 of GitLab.
What does CVE-2023-6955 allow an attacker to do?
CVE-2023-6955 allows an attacker to create a workspace in one group that is improperly associated with an agent from another group.
Is there a workaround for CVE-2023-6955?
There is no specific workaround for CVE-2023-6955 other than applying the necessary software updates as soon as possible.