What is the vulnerability ID of this GitLab issue?

The vulnerability ID of this GitLab issue is CVE-2023-5198.

How can a removed project member exploit this vulnerability?

A removed project member can exploit this vulnerability by writing to protected branches using deploy keys.

What is the severity of CVE-2023-5198?

The severity of CVE-2023-5198 is medium.

How can I fix this vulnerability in GitLab?

To fix this vulnerability, you should update GitLab to version 16.2.7 or later for versions prior to 16.3.5, and update to version 16.3.5 or later for versions starting from 16.3 before 16.4.1.

Vulnerability/
CVE-2023-5198

medium

4.3

CWE

284 863

29/9/2023

21/11/2024

CVE-2023-5198: Incorrect Authorization in GitLab

Q: What versions of GitLab are affected by this vulnerability?

This vulnerability affects all versions prior to 16.2.7, all versions starting from 16.3 before 16.3.5, and all versions starting from 16.4 before 16.4.1 of GitLab.

First published: Fri Sep 29 2023(Updated: )

An issue has been discovered in GitLab affecting all versions prior to 16.2.7, all versions starting from 16.3 before 16.3.5, and all versions starting from 16.4 before 16.4.1. It was possible for a removed project member to write to protected branches using deploy keys.

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

Affected Software	Affected Version	How to fix
GitLab GitLab	>=8.15<16.2.8
GitLab GitLab	>=8.15<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
	>=8.15<16.2.8
	>=8.15<16.2.8
	>=16.3.0<16.3.5
	>=16.3.0<16.3.5
	=16.4.0
	=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 of this GitLab issue?
The vulnerability ID of this GitLab issue is CVE-2023-5198.
What versions of GitLab are affected by this vulnerability?
This vulnerability affects all versions prior to 16.2.7, all versions starting from 16.3 before 16.3.5, and all versions starting from 16.4 before 16.4.1 of GitLab.
How can a removed project member exploit this vulnerability?
A removed project member can exploit this vulnerability by writing to protected branches using deploy keys.
What is the severity of CVE-2023-5198?
The severity of CVE-2023-5198 is medium.
How can I fix this vulnerability in GitLab?
To fix this vulnerability, you should update GitLab to version 16.2.7 or later for versions prior to 16.3.5, and update to version 16.3.5 or later for versions starting from 16.3 before 16.4.1.

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
collector/mitre-cve
source/MITRE
agent/weakness
agent/title
agent/last-modified-date
agent/tags
collector/nvd-api
source/NVD
vendor/gitlab
canonical/gitlab gitlab
version/gitlab gitlab/8.15
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.