CVE-2024-10043: Incorrect Authorization in GitLab

Published Dec 11, 2024
·
Updated

An issue has been discovered in GitLab EE affecting all versions starting from 14.3 before 17.4.6, all versions starting from 17.5 before 17.5.4 all versions starting from 17.6 before 17.6.2, that allows group users to view confidential incident title through the Wiki History Diff feature, potentially leading to information disclosure.

Affected Software

5 affected componentsFixes available
GitLab GitLab EE>=14.3, <17.4.6, >=17.5, <17.5.4, >=17.6, <17.6.2
GitLab GitLab>=14.3.0<17.4.6
GitLab GitLab>=17.5.0<17.5.4
GitLab GitLab>=17.6.0<17.6.2
GitLab GitLab EE>=14.3<17.4.6, >=17.5<17.5.4, >=17.6<17.6.2
17.4.617.5.417.6.2

Remediation

Information

Upgrade to versions 17.4.6, 17.5.4, 17.6.2 or above.

Event History

Dec 12, 2024
CVE Published
via MITRE·12:02 PM
Data Sourced
via MITRE·12:02 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 22, 2026
Data Sourced
via GitLab·08:55 AM
DescriptionSeverityAffected Software
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-2024-10043?

CVE-2024-10043 has a high severity rating due to its potential to expose confidential incident titles to unauthorized users.

2

How do I fix CVE-2024-10043?

To fix CVE-2024-10043, upgrade your GitLab EE installation to version 17.5.4 or later, or to version 17.6.2 or later.

3

What versions of GitLab EE are affected by CVE-2024-10043?

CVE-2024-10043 affects GitLab EE versions from 14.3 up to but not including 17.4.6, from 17.5 up to but not including 17.5.4, and from 17.6 up to but not including 17.6.2.

4

Who is impacted by CVE-2024-10043?

Group users within affected GitLab EE versions can view confidential incident titles through the Wiki History Diff feature.

5

What should I do if I cannot upgrade due to compatibility issues with CVE-2024-10043?

If you cannot upgrade, consider implementing access controls or limiting group user permissions to mitigate the risks associated with CVE-2024-10043.

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