CVE-2023-7028
GitLab Community and Enterprise Editions Improper Access Control Vulnerability
GitLab CE/EE
An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 1 May 2024. US federal agencies were required to remediate it by 22 May 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 94.6%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Frequently asked questions
Is CVE-2023-7028 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2023-7028.
What does CVE-2023-7028 affect?
CVE-2023-7028 affects GitLab CE/EE. An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address.
How severe is CVE-2023-7028?
CVE-2023-7028 is rated CRITICAL with a CVSS base score of 10. EPSS puts the probability of exploitation in the next 30 days at 94.6%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 May 2024.
How should organisations respond to CVE-2023-7028?
Apply the vendor patch for GitLab CE/EE as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.