CVE-2023-3511: Auditor users can create merge requests on projects they don't have access to
An issue has been discovered in GitLab EE affecting all versions starting from 8.17 before 16.4.4, all versions starting from 16.5 before 16.5.4, all versions starting from 16.6 before 16.6.2. It was possible for auditor users to fork and submit merge requests to private projects they're not a member of.
Other sources
An issue has been discovered in GitLab EE affecting all versions starting from 8.17 before 16.4.4, all versions starting from 16.5 before 16.5.4, all versions starting from 16.6 before 16.6.2. It was possible for auditor users to fork and submit merge requests to private projects they’re not a member of. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N, 2.0). It is now mitigated in the latest release and is assigned CVE-2023-3511.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2023-3511?
CVE-2023-3511 has a medium severity rating due to its impact on the permissions of auditor users.
How do I fix CVE-2023-3511?
To fix CVE-2023-3511, upgrade GitLab EE to version 16.4.4 or later, 16.5.4 or later, or 16.6.2 or later.
What versions of GitLab EE are affected by CVE-2023-3511?
CVE-2023-3511 affects GitLab EE versions from 8.17 up to but not including 16.4.4, from 16.5 up to but not including 16.5.4, and from 16.6 up to but not including 16.6.2.
Who can be affected by CVE-2023-3511?
Auditor users in GitLab EE can be affected by CVE-2023-3511 as it allows them to fork and submit merge requests to private projects.
What is the exploitability of CVE-2023-3511?
CVE-2023-3511 can be exploited by auditor users to gain unauthorized access to private project functionalities.