dbcve.org
GitLabApplication

CVE-2024-1347

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-25
Fix available
A fix is available. Upgrade to 16.9.6 / 16.10.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue has been discovered in GitLab CE/EE affecting all versions before 16.9.6, all versions starting from 16.10 before 16.10.4, all versions starting from 16.11 before 16.11.1. Under certain conditions, an attacker through a crafted email address may be able to bypass domain based restrictions on an instance or a group.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

GitLab CE/EE allows users to restrict email domains at the instance or group level for user registration/email verification. This vulnerability allows attackers to bypass these domain restrictions by using a crafted email address that manipulates how GitLab parses or validates the domain portion of the email.

MitigationUpgrade GitLab to version 16.9.6, 16.10.4, 16.11.1 or later. After upgrading, verify that domain-based restrictions on instance and group settings are properly enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:< 16.9.6>= 16.10.0, < 16.10.4= 16.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Access the GitLab admin panel and navigate to the Help section in the top right corner, or use the API endpoint: curl -s https://your-gitlab-instance/api/v4/version, or run: sudo gitlab-rake gitlab:env:info
    Affected if The version returned is below 16.9.6, between 16.10.0-16.10.3 inclusive, or exactly 16.11.0
  2. Verify email domain restrictions are configured
    Go to Admin Area > Settings > Sign-up restrictions > Approved email domains, or check Group > Settings > General > Restrict email domains for group-level restrictions
    Affected if Email domain restrictions are enabled and a list of allowed domains is configured
  3. Confirm registration or email verification is enabled
    Check Admin Area > Settings > Sign-up restrictions > Sign-up enabled, and verify that email confirmation is required under Authentication settings
    Affected if Users can register new accounts or email verification is available for new users
  4. Test email domain parsing behavior
    Attempt to register a user with a crafted email containing the restricted domain in an unusual format (for example, using unusual separators or encoding in the domain portion) and observe if the restriction is bypassed
    Affected if The registration succeeds when it should be blocked by the configured domain restrictions

You are affected if your GitLab version falls within the vulnerable ranges AND email domain restrictions are enabled, allowing bypassed registrations with crafted email addresses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.9.6 / 16.10.4 or later
Fixed in 16.9.616.10.4
Interim mitigation

Upgrade GitLab to version 16.9.6, 16.10.4, 16.11.1 or later. After upgrading, verify that domain-based restrictions on instance and group settings are properly enforced.

Recommended fix Moderate confidence

16.9.6, 16.10.4, or 16.11.1 depending on your current version branch

  1. 1. Identify your current GitLab version by running `sudo gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. 2. Choose the appropriate fixed version based on your current branch: upgrade to 16.9.6 if on 16.9.x, 16.10.4 if on 16.10.x, or 16.11.1 if on 16.11.x
  3. 3. Back up your GitLab data using `sudo gitlab-backup-create` or your documented backup procedure
  4. 4. For package installations (Omnibus), update using: `sudo apt-get update && sudo apt-get install gitlab-ce` (for CE) or `sudo apt-get install gitlab-ee` (for EE)
  5. 5. For source installations, follow the upgrade path in GitLab's documentation for upgrading from source
  6. 6. After upgrade completes, run `sudo gitlab-ctl reconfigure`
  7. 7. Verify the upgrade was successful and test that domain-based restrictions on users and groups are functioning correctly
  8. 8. Confirm the new version by running `sudo gitlab-rake gitlab:env:info`
Caveat Review GitLab 16.10 and 16.11 release notes for any breaking changes or deprecations that may affect your instance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1347 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data