dbcve.org
GitLabApplication

CVE-2024-1525

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 16.7.6 / 16.8.3 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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 starting from 16.1 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions starting from 16.9 before 16.9.1. Under some specialized conditions, an LDAP user may be able to reset their password using their verified secondary email address and sign-in using direct authentication with the reset password, bypassing LDAP.

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 · high confidence

In affected GitLab CE/EE versions (16.1-16.7.6, 16.8-16.8.3, 16.9-16.9.1), an LDAP user with a verified secondary email address can reset their account password through the standard password reset flow using that secondary email. This allows them to subsequently authenticate directly (non-LDAP) with the new password, bypassing the LDAP authentication requirement that should be enforced for their account.

MitigationUpgrade GitLab to version 16.7.6, 16.8.3, 16.9.1 or later. In the interim, consider disabling the password reset feature for LDAP-synced users or enforcing LDAP-only authentication policies.

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.1, < 16.7.6>= 16.8, < 16.8.3= 16.9.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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. Determine your GitLab version
    Run 'gitlab-rake gitlab:env:info' or check the GitLab admin dashboard under Help > Version. Alternatively, check /opt/gitlab/version on the server.
    Affected if The installed version falls within 16.1 to 16.7.6, 16.8 to 16.8.3, or equals 16.9.0 or 16.9.1.
  2. Verify LDAP integration is enabled
    Navigate to Admin Area > LDAP in the GitLab web UI, or check the gitlab.yml configuration file for LDAP settings.
    Affected if LDAP is configured and active in the GitLab instance.
  3. Identify LDAP-synced users with secondary emails
    Query the GitLab database: select users with LDAP identity provider and verified secondary emails. In the Admin Area, review user accounts that are LDAP-synced and have a secondary email address listed.
    Affected if There exist LDAP users who have a verified secondary email address registered in their account.
  4. Confirm password reset is accessible
    Attempt to access the password reset flow at /users/password/new or verify the password reset feature is not disabled in GitLab settings.
    Affected if The standard password reset flow is available and not restricted for LDAP-synced users.

You are affected if your GitLab version is within the vulnerable range, LDAP is enabled, and there are LDAP-synced users with verified secondary email addresses who could reset their password and bypass LDAP authentication.

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.7.6 / 16.8.3 or later
Fixed in 16.7.616.8.3
Interim mitigation

Upgrade GitLab to version 16.7.6, 16.8.3, 16.9.1 or later. In the interim, consider disabling the password reset feature for LDAP-synced users or enforcing LDAP-only authentication policies.

Recommended fix High confidence

Upgrade to GitLab 16.7.6, 16.8.3, or 16.9.1 (or later) depending on your current version branch

  1. Identify the currently running GitLab version using the Rails console (sudo gitlab-rails console) or the admin area UI
  2. Determine which upgrade path applies based on current version: if >=16.1 and <16.7.6, target 16.7.6; if >=16.8 and <16.8.3, target 16.8.3; if 16.9.0, target 16.9.1
  3. Plan the upgrade following GitLab's standard upgrade documentation for your deployment method (omnibus, source, etc.)
  4. Create a full backup of the GitLab instance before upgrading
  5. Stop GitLab services before the upgrade
  6. Install the target patched version (16.7.6, 16.8.3, or 16.9.1 as appropriate)
  7. Reconfigure and restart GitLab services
  8. Verify the upgrade completed successfully and GitLab is operational
Caveat Review GitLab release notes for any breaking changes between your current version and the target version, especially regarding LDAP authentication behavior

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1525 — 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-1525 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