CVE-2024-1525: LDAP user can reset password using secondary email and login using direct authentication

Published Feb 21, 2024
·
Updated

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.1 before 16.7.2, all versions starting from 16.8 before 16.8.2, all versions starting from 16.9 before 16.9.2. 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. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N, 5.3). It is now mitigated in the latest release and is assigned CVE-2024-1525.

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
GitLab GitLab>=16.1<16.7.6
GitLab GitLab>=16.8<16.8.3
GitLab GitLab=16.9.0
GitLab GitLab>=16.1<16.7.2, >=16.8<16.8.2, >=16.9<16.9.2
16.7.216.8.216.9.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.7.2Fixed in 16.8.2Fixed in 16.9.2
  2. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 16.7.6
  3. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 16.8.3
  4. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 16.9.1

Event History

Feb 21, 2024
CVE Published
via MITRE·11:30 PM
Data Sourced
via MITRE·11:30 PM
RemedyDescriptionSeverityWeakness
Feb 22, 2024
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
Apr 22, 2026
Data Sourced
via GitLab·08:52 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-1525?

CVE-2024-1525 is classified as a medium severity vulnerability affecting GitLab.

2

How do I fix CVE-2024-1525?

To fix CVE-2024-1525, you should upgrade GitLab to version 16.7.6, 16.8.3, or any version beyond 16.9.1.

3

Which GitLab versions are affected by CVE-2024-1525?

CVE-2024-1525 affects GitLab versions starting from 16.1 before 16.7.6, 16.8 before 16.8.3, and 16.9 before 16.9.1.

4

What type of issue is CVE-2024-1525 related to?

CVE-2024-1525 is related to an LDAP user being able to reset their password under specific conditions.

5

Is there a workaround for CVE-2024-1525?

Currently, the recommended solution for CVE-2024-1525 is to update to an unaffected version of GitLab, as there is no known workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203