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.

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).

Vulnerability/
CVE-2023-3920

medium

4.3

CWE

345 863

29/9/2023

8/10/2024

CVE-2023-3920: Incorrect Authorization in GitLab

Q: 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.

First published: Fri Sep 29 2023(Updated: )

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.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab GitLab	>=11.2<16.2.8
GitLab GitLab	>=11.2<16.2.8
GitLab GitLab	>=16.3.0<16.3.5
GitLab GitLab	>=16.3.0<16.3.5
GitLab GitLab	=16.4.0
GitLab GitLab	=16.4.0

Remedy

Upgrade to version 16.4.1, 16.3.5, 16.2.8

Never miss a vulnerability like this again

Reference Links

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).

agent/references
agent/author
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/description
agent/remedy
agent/severity
agent/first-publish-date
agent/event
agent/tags
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/title
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/gitlab
canonical/gitlab gitlab
version/gitlab gitlab/11.2
version/gitlab gitlab/16.3.0
version/gitlab gitlab/16.4.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.