GitLab Community Edition/Enterprise Edition up to 17.5.4/17.6.2/17.7.0 incorrect user management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.5.4/17.6.2/17.7.0. It has been classified as problematic. This affects an unknown part. The manipulation leads to incorrect user management. This vulnerability is uniquely identified as CVE-2024-13041. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.5.4/17.6.2/17.7.0. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a incorrect user management vulnerability. Using CWE to declare the problem leads to CWE-286. The product does not properly manage a user within its environment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in GitLab CE/EE affecting all versions starting from 16.4 prior to 17.5.5, starting from 17.6 prior to 17.6.3, and starting from 17.7 prior to 17.7.1. When a user is created via the SAML provider, the external groups setting overrides the external provider configuration. As a result, the user may not be marked as external thereby giving those users access to internal projects or groups.
The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2024-13041 since 12/30/2024. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 213635 (GitLab 16.4 < 17.5.5 / 17.6 < 17.6.3 / 17.7 < 17.7.1 (CVE-2024-13041)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.5.5, 17.6.3 or 17.7.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (213635). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CNA Base Score: 4.2
CNA Vector (GitLab): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Incorrect user managementCWE: CWE-286
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 213635
Nessus Name: GitLab 16.4 < 17.5.5 / 17.6 < 17.6.3 / 17.7 < 17.7.1 (CVE-2024-13041)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.5.5/17.6.3/17.7.1
Timeline
12/30/2024 🔍01/09/2025 🔍
01/09/2025 🔍
08/05/2025 🔍
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Status: Confirmed
CVE: CVE-2024-13041 (🔍)
GCVE (CVE): GCVE-0-2024-13041
GCVE (VulDB): GCVE-100-290897
Entry
Created: 01/09/2025 07:50Updated: 08/05/2025 17:55
Changes: 01/09/2025 07:50 (63), 01/09/2025 19:56 (2), 08/05/2025 17:55 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.