CVE-2023-3920: Incorrect Authorization in GitLab
An issue has been discovered in GitLab affecting all versions starting from 11.2 before 16.2.8, all versions starting from 16.3 before 16.3.5, all versions starting from 16.4 before 16.4.1. It was possible that a maintainer to create a fork relationship between existing projects contrary to the documentation.
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.2.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.3.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.4.1
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2023-3920.
What is the severity of CVE-2023-3920?
The severity of CVE-2023-3920 is medium with a CVSS score of 4.3.
Which versions of GitLab are affected by CVE-2023-3920?
All versions starting from 11.2 before 16.2.8, all versions starting from 16.3 before 16.3.5, and version 16.4.0 of GitLab are affected by CVE-2023-3920.
What is the impact of CVE-2023-3920?
CVE-2023-3920 allows a maintainer to create a fork relationship between existing projects contrary to the documentation, which may lead to unauthorized access.
Are there any references for CVE-2023-3920?
Yes, the following references are available: [Link 1](https://gitlab.com/gitlab-org/gitlab/-/issues/417481), [Link 2](https://hackerone.com/reports/2058121).