What is the vulnerability ID?

The vulnerability ID is CVE-2023-3444.

What versions of GitLab are affected by this vulnerability?

All versions of GitLab starting from 15.3 before 15.11.10, and all versions starting from 16.0 before 16.0.6, including all versions starting from 16.1 before 16.1.1.

What is the severity of CVE-2023-3444?

The severity of CVE-2023-3444 is medium with a CVSS score of 6.5.

Are there any known fixes for this vulnerability?

Yes, GitLab has released patches to address this vulnerability. It is recommended to update to the latest version of GitLab.

Vulnerability/
CVE-2023-3444

medium

6.5

CWE

74 99 863

13/7/2023

5/5/2025

CVE-2023-3444: Incorrect Authorization in GitLab

Q: What is the impact of this vulnerability?

This vulnerability allows an attacker to merge arbitrary code into protected branches in GitLab.

First published: Thu Jul 13 2023(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.3 before 15.11.10, all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1, which allows an attacker to merge arbitrary code into protected branches.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=15.3.0<15.11.10
GitLab	>=15.3.0<15.11.10
GitLab	>=16.0.0<16.0.6
GitLab	>=16.0.0<16.0.6
GitLab	>=16.1.0<16.1.1
GitLab	>=16.1.0<16.1.1

Remedy

Upgrade to versions 15.11.10, 16.0.6, 16.1.1 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the vulnerability ID?
The vulnerability ID is CVE-2023-3444.
What versions of GitLab are affected by this vulnerability?
All versions of GitLab starting from 15.3 before 15.11.10, and all versions starting from 16.0 before 16.0.6, including all versions starting from 16.1 before 16.1.1.
What is the severity of CVE-2023-3444?
The severity of CVE-2023-3444 is medium with a CVSS score of 6.5.
What is the impact of this vulnerability?
This vulnerability allows an attacker to merge arbitrary code into protected branches in GitLab.
Are there any known fixes for this vulnerability?
Yes, GitLab has released patches to address this vulnerability. It is recommended to update to the latest version of GitLab.

collector/nvd-latest
agent/references
agent/author
agent/type
agent/description
agent/remedy
agent/severity
agent/first-publish-date
agent/event
agent/weakness
agent/title
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/15.3.0
version/gitlab/16.0.0
version/gitlab/16.1.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.