What is CVE-2023-5995?

CVE-2023-5995 is a vulnerability in GitLab EE that allows an attacker to abuse the policy bot to gain access to internal projects.

What versions of GitLab EE are affected by CVE-2023-5995?

All versions starting from 16.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, and version 16.6.0 are affected by CVE-2023-5995.

How severe is CVE-2023-5995?

CVE-2023-5995 has a severity rating of 7.5, making it a high-severity vulnerability.

How can an attacker exploit CVE-2023-5995?

An attacker can exploit CVE-2023-5995 by using the policy bot to gain unauthorized access to internal projects.

Where can I find more information about CVE-2023-5995?

More information about CVE-2023-5995 can be found at the following references: [GitLab issue](https://gitlab.com/gitlab-org/gitlab/-/issues/425361) and [HackerOne report](https://hackerone.com/reports/2138880).

Vulnerability/
CVE-2023-5995

high

7.5

CWE

284

EPSS

0.121%

1/12/2023

6/12/2023

CVE-2023-5995: Improper Access Control in GitLab

First published: Fri Dec 01 2023(Updated: )

An issue has been discovered in GitLab EE affecting all versions starting from 16.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. It was possible for an attacker to abuse the policy bot to gain access to internal projects.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
Gitlab Gitlab	>=16.2.0<16.4.3
Gitlab Gitlab	>=16.5.0<16.5.3
Gitlab Gitlab	=16.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2023-5995?
CVE-2023-5995 is a vulnerability in GitLab EE that allows an attacker to abuse the policy bot to gain access to internal projects.
What versions of GitLab EE are affected by CVE-2023-5995?
All versions starting from 16.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, and version 16.6.0 are affected by CVE-2023-5995.
How severe is CVE-2023-5995?
CVE-2023-5995 has a severity rating of 7.5, making it a high-severity vulnerability.
How can an attacker exploit CVE-2023-5995?
An attacker can exploit CVE-2023-5995 by using the policy bot to gain unauthorized access to internal projects.
Where can I find more information about CVE-2023-5995?
More information about CVE-2023-5995 can be found at the following references: [GitLab issue](https://gitlab.com/gitlab-org/gitlab/-/issues/425361) and [HackerOne report](https://hackerone.com/reports/2138880).

agent/author
agent/description
agent/epss
agent/event
agent/first-publish-date
agent/last-modified-date
agent/references
agent/remedy
agent/severity
agent/softwarecombine
agent/tags
agent/title
agent/type
agent/weakness
collector/epss-latest
source/FIRST
collector/mitre-cve
collector/nvd-api
vendor/gitlab
canonical/gitlab gitlab
version/gitlab gitlab/16.2.0
version/gitlab gitlab/16.5.0
version/gitlab gitlab/16.6.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.