What is the vulnerability ID for this issue?

The vulnerability ID for this issue is CVE-2023-3413.

Which version of GitLab is affected by this vulnerability?

All versions starting from 16.2 before 16.2.8, all versions starting from 16.3 before 16.3.5, and version 16.4.0 are affected by this vulnerability.

What is the severity rating of CVE-2023-3413?

CVE-2023-3413 has a severity rating of 7.5 (high).

How can an attacker exploit this vulnerability?

An attacker can exploit this vulnerability by creating a fork of a project before changing its visibility, allowing them to read the source code of the project.

Are there any patches or fixes available for this vulnerability?

Yes, GitLab has released patches for this vulnerability. It is recommended to update to the latest patched version of GitLab to mitigate the risk.

Vulnerability/
CVE-2023-3413

high

7.5

CWE

200 201

29/9/2023

3/10/2024

CVE-2023-3413: Insertion of Sensitive Information Into Sent Data in GitLab

First published: Fri Sep 29 2023(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 16.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 to read the source code of a project through a fork created before changing visibility to only project members.

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

Affected Software	Affected Version	How to fix
GitLab GitLab	>=16.2<16.2.8
GitLab GitLab	>=16.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 versions 16.4.1, 16.3.5, 16.2.8 or above.

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-3413.
Which version of GitLab is affected by this vulnerability?
All versions starting from 16.2 before 16.2.8, all versions starting from 16.3 before 16.3.5, and version 16.4.0 are affected by this vulnerability.
What is the severity rating of CVE-2023-3413?
CVE-2023-3413 has a severity rating of 7.5 (high).
How can an attacker exploit this vulnerability?
An attacker can exploit this vulnerability by creating a fork of a project before changing its visibility, allowing them to read the source code of the project.
Are there any patches or fixes available for this vulnerability?
Yes, GitLab has released patches for this vulnerability. It is recommended to update to the latest patched version of GitLab to mitigate the risk.

agent/references
agent/author
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/description
agent/severity
agent/remedy
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/16.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.