Identity impersonation via reordered email validation
Published May 3, 2023 · Updated Jan 30, 2025
Improper email verification in affected GitLab CE/EE releases before 16.0.2 allows remote authenticated users to impersonate commit identities. User-update logic changes the current email before comparing public and commit email values with it, allowing an unverified attacker-selected address to pass. A low-privileged account and crafted authenticated settings request are required; successful use bypasses commit-email restrictions and misrepresents account identity.
Summary
What happened
Improper email verification in affected GitLab CE/EE releases before 16.0.2 allows remote authenticated users to impersonate commit identities. User-update logic changes the current email before comparing public and commit email values with it, allowing an unverified attacker-selected address to pass. A low-privileged account and crafted authenticated settings request are required; successful use bypasses commit-email restrictions and misrepresents account identity.
The record
- CVE
- CVE-2023-1204
- Published
- May 3, 2023
- Updated
- Jan 30, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-347, T1036
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=10.0, <12.9.8
- Affected versionversion=>=12.10, <12.10.7
- Affected versionversion=>=13.0, <13.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Authenticated public and commit email validation-bypass reproductionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo