CVE-2023-7028: GitLab Community and Enterprise Editions Improper Access Control Vulnerability

Published Jan 11, 2024
·
Updated

An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address.

Other sources

GitLab Community and Enterprise Editions contain an improper access control vulnerability. This allows an attacker to trigger password reset emails to be sent to an unverified email address to ultimately facilitate an account takeover.

CISA

Credit

0xB455

Affected Software

16 affected componentsFixes available
GitLab GitLab>=16.1.0<16.1.6
GitLab GitLab>=16.1.0<16.1.6
GitLab GitLab>=16.2.0<16.2.9
GitLab GitLab>=16.2.0<16.2.9
GitLab GitLab>=16.3.0<16.3.7
GitLab GitLab>=16.3.0<16.3.7
GitLab GitLab>=16.4.0<16.4.5
GitLab GitLab>=16.4.0<16.4.5
GitLab GitLab>=16.5.0<16.5.6
GitLab GitLab>=16.5.0<16.5.6
GitLab GitLab>=16.6.0<16.6.4
GitLab GitLab>=16.6.0<16.6.4
GitLab GitLab>=16.7.0<16.7.2
GitLab GitLab>=16.7.0<16.7.2
GitLab GitLab CE/EE
GitLab GitLab>=16.1<16.1.6, >=16.2<16.2.9, >=16.3<16.3.7, >=16.4<16.4.5, >=16.5<16.5.6, >=16.6<16.6.4, >=16.7<16.7.2
16.1.616.2.916.3.716.4.516.5.616.6.416.7.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.1.6Fixed in 16.2.9Fixed in 16.3.7Fixed in 16.4.5Fixed in 16.5.6Fixed in 16.6.4Fixed in 16.7.2
  2. Upgrade

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

    Fixed in 16.7.2
  3. Upgrade

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

    Fixed in 16.6.4
  4. Upgrade

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

    Fixed in 16.5.6
  5. Upgrade

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

    Fixed in 16.4.5
  6. Upgrade

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

    Fixed in 16.3.7
  7. Upgrade

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

    Fixed in 16.2.9
  8. Upgrade

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

    Fixed in 16.1.6

Event History

Jan 12, 2024
CVE Published
via MITRE·01:56 PM
Data Sourced
via MITRE·01:56 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeaknessAffected Software
News Published
05:54 PM
Jan 15, 2024
News Published
05:36 PM
Jan 24, 2024
News Published
via BleepingComputer·05:55 PM
News Published
via BleepingComputer·05:56 PM
Mar 14, 2024
Exploit Published
via ExploitDB·12:00 AM
Known Exploited
via ExploitDB·12:00 AM
May 1, 2024
News Published
via BleepingComputer·04:29 PM
May 2, 2024
News Published
via The Register·02:15 PM
News Published
via The Register·02:18 PM
May 23, 2024
News Published
via BleepingComputer·05:43 PM
Jul 10, 2024
News Published
via BleepingComputer·08:08 PM
Apr 22, 2026
Data Sourced
via GitLab·08:52 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-7028?

The severity of CVE-2023-7028 is currently classified as critical due to the potential for account takeover through zero-click attacks.

2

How do I fix CVE-2023-7028?

To fix CVE-2023-7028, update GitLab to version 16.1.6, 16.2.9, 16.3.7, 16.4.5, 16.5.6, 16.6.4, or 16.7.2, or later.

3

What versions are affected by CVE-2023-7028?

CVE-2023-7028 affects all GitLab CE/EE versions from 16.1.0 to prior versions specified up to 16.7.2.

4

Who is impacted by CVE-2023-7028?

All users of GitLab CE/EE running affected versions prior to the fix are at risk of this vulnerability.

5

Is CVE-2023-7028 being actively exploited?

Yes, CVE-2023-7028 is reported to be actively exploited in the wild, increasing the urgency for users to apply updates.

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