CVE-2023-4700

Public Exploit
Missing Authorization in GitLab

Description

An authorization issue affecting GitLab EE affecting all versions from 14.7 prior to 16.3.6, 16.4 prior to 16.4.2, and 16.5 prior to 16.5.1, allowed a user to run jobs in protected environments, bypassing any required approvals.

Remediation

Solution:

  • Upgrade to versions 16.3.6, 16.4.2, 16.5.1 or above.

Category

3.5
CVSS
Severity: Low
CVSS 3.1 •
EPSS 0.01%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/421937 issue tracking broken link permissions required
https://hackerone.com/reports/2129826 broken link exploit permissions required technical description

Frequently Asked Questions

What is the severity of CVE-2023-4700?
CVE-2023-4700 has been scored as a low severity vulnerability.
How to fix CVE-2023-4700?
To fix CVE-2023-4700: Upgrade to versions 16.3.6, 16.4.2, 16.5.1 or above.
Is CVE-2023-4700 being actively exploited in the wild?
It is possible that CVE-2023-4700 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-4700?
CVE-2023-4700 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.