CVE-2023-7028: GitLab Community and Enterprise Editions Improper Access Control Vulnerability

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run GitLab GitLab CE/EE. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2024-05-01, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2024-05-22; treat that as the outer limit, not the target.
• EPSS 94.5%, percentile 99.9: FIRST’s model estimates a 94.5% chance of exploitation activity in the next 30 days, higher than 99.9% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Editorial verdict: Act now. GitLab Password Reset Flaw Enables Account Takeover — Any self-managed GitLab still on 16.1 through 16.7.1 lets anyone take over accounts without 2FA by email alone; upgrade immediately and turn on 2FA.

What it is

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.

CISA’s summary

GitLab Community and Enterprise Editions contain an improper access control vulnerability. This allows an attacker to trigger password reset emails to be sent to an unverified email address to ultimately facilitate an account takeover.

Weakness type: CWE-640, CWE-284.

Product: GitLab GitLab CE/EE · Assigned by: GitLab · Published: 2024-01-12

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2024-05-01; federal due date 2024-05-22. Known ransomware use: Unknown.
• CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
• CISA SSVC assessment: exploitation active, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 94.46% probability of exploitation activity in the next 30 days; percentile 99.9.

Timeline

• 2024-01-11 — erroneo.us brief: GitLab Password Reset Flaw Enables Account Takeover
• 2024-01-12 — CVE record published by GitLab
• 2024-05-01 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2024-05-22 — CISA remediation deadline for US federal agencies
• 2026-08-15 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (about.gitlab.com) about.gitlab.com

Vulnerability records

1. CVE.org record CVE-2023-7028 cve.org
2. NVD entry CVE-2023-7028 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

Other references from the CVE record and advisory

1. GitLab Issue #436084 gitlab.com
2. HackerOne Bug Bounty Report #2293343 hackerone.com
3. vicarius.io vicarius.io

All exploited GitLab vulnerabilities · Today’s Security Digest