Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-1347 Overview
CVE-2024-1347 is an authentication bypass vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE). The flaw allows an attacker to bypass domain-based access restrictions on an instance or group by submitting a crafted email address. The issue is classified under CWE-290: Authentication Bypass by Spoofing.
GitLab patched the issue in versions 16.9.6, 16.10.4, and 16.11.1. All prior releases in these branches are affected.
Critical Impact
Attackers can register or join groups and instances that enforce email domain allowlists, undermining tenant isolation and group membership controls.
Affected Products
- GitLab Community Edition (CE) — all versions before 16.9.6
- GitLab Enterprise Edition (EE) — versions 16.10 before 16.10.4
- GitLab CE/EE — versions 16.11 before 16.11.1
Discovery Timeline
- 2024-04-25 - CVE-2024-1347 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-1347
Vulnerability Analysis
GitLab administrators and group owners can restrict sign-up or membership to users whose email addresses belong to approved domains. This domain allowlist mechanism assumes the server-side parser extracts the same domain that downstream validation checks against.
CVE-2024-1347 breaks that assumption. A crafted email address causes the restriction check to accept an input that the mail delivery layer treats as a different, non-approved domain. The attacker gains access as if they held an address inside the trusted domain.
The reported impact is limited to integrity. The attacker does not read protected data directly, but gains unauthorized membership that normally requires an approved identity.
Root Cause
The root cause is inconsistent parsing of RFC 5322 email address components during allowlist validation. GitLab's domain extraction logic diverges from strict address parsing when encountering edge cases such as embedded quoting, comments, or multiple @ tokens.
Because the authorization decision relies on string-level matching rather than normalized identity, the attacker-controlled portion of the address determines routing while the trusted portion satisfies the policy check. This is a classic authentication-bypass-by-spoofing pattern.
Attack Vector
Exploitation requires only network access to the GitLab instance and no prior authentication. The attacker submits the crafted email address during sign-up, group invitation acceptance, or email change workflows that enforce the domain restriction.
Technical details are tracked in the vendor issue GitLab Issue #441093 and the researcher submission HackerOne Report #2355565.
No verified proof-of-concept code has been published. The vulnerability mechanism is best understood by reviewing the referenced GitLab issue and HackerOne disclosure.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2024-1347
Indicators of Compromise
- New user accounts whose registered email address contains unusual syntax such as nested quoting, multiple @ characters, or encoded whitespace.
- Group membership additions where the user's effective mail delivery domain differs from the domain shown in the GitLab UI.
- Audit log entries showing successful registration or group join events that would normally be blocked by the configured domain allowlist.
Detection Strategies
- Query the GitLab users table and compare the email field against the configured allowed domains using strict RFC 5322 parsing. Flag any mismatch.
- Review audit_events for user_created and group_member_added actions since the earliest vulnerable release was deployed.
- Correlate GitLab authentication events with upstream mail delivery logs to identify addresses that resolve to unexpected external domains.
Monitoring Recommendations
- Enable GitLab audit logging for user creation, group invitation, and email change events and forward them to a central SIEM.
- Alert on registrations containing suspicious email syntax such as ", (, ), or multiple @ symbols in the local part.
- Baseline normal registration volume per group and alert on bursts following the public disclosure date.
How to Mitigate CVE-2024-1347
Immediate Actions Required
- Upgrade GitLab CE/EE to 16.9.6, 16.10.4, or 16.11.1 or later as applicable to your branch.
- Audit all users added to domain-restricted groups and instances since January 2024 and remove accounts that do not satisfy the allowlist under strict parsing.
- Rotate any secrets, tokens, or deploy keys that unauthorized members could have accessed through group inheritance.
Patch Information
GitLab fixed CVE-2024-1347 in versions 16.9.6, 16.10.4, and 16.11.1. The remediation is tracked in GitLab Issue #441093. Apply the upgrade following GitLab's standard zero-downtime or offline upgrade procedure for your deployment topology.
Workarounds
- If immediate patching is not possible, disable public sign-up and require administrator approval for all new accounts on affected instances.
- Temporarily remove domain-based allowlists on sensitive groups and replace them with explicit user invitations until the upgrade is complete.
- Restrict access to the GitLab instance at the network layer to known corporate IP ranges while the patch is scheduled.
# Disable public sign-up via the Rails console as a temporary mitigation
sudo gitlab-rails runner "ApplicationSetting.current.update!(signup_enabled: false)"
# Require admin approval for any new user that is created
sudo gitlab-rails runner "ApplicationSetting.current.update!(require_admin_approval_after_user_signup: true)"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

