GitLab Enterprise Edition up to 17.4.5/17.5.3/17.6.1 Wiki History Diff authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in GitLab Enterprise Edition up to 17.4.5/17.5.3/17.6.1. Affected by this vulnerability is an unknown functionality of the component Wiki History Diff. The manipulation results in authorization. This vulnerability is identified as CVE-2024-10043. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in GitLab Enterprise Edition up to 17.4.5/17.5.3/17.6.1. Affected is an unknown functionality of the component Wiki History Diff. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality. CVE summarizes:
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.
The weakness was released by mateuszek as 499577. The advisory is shared for download at gitlab.com. This vulnerability is traded as CVE-2024-10043 since 10/16/2024. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 212687 (GitLab 14.3 < 17.4.6 / 17.5 < 17.5.4 / 17.6 < 17.6.2 (CVE-2024-10043)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.4.6, 17.5.4 or 17.6.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (212687). Once again VulDB remains the best source for 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: 3.1VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 3.1
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: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
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: 212687
Nessus Name: GitLab 14.3 < 17.4.6 / 17.5 < 17.5.4 / 17.6 < 17.6.2 (CVE-2024-10043)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Enterprise Edition 17.4.6/17.5.4/17.6.2
Timeline
10/16/2024 🔍12/12/2024 🔍
12/12/2024 🔍
07/12/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 499577
Researcher: mateuszek
Status: Confirmed
CVE: CVE-2024-10043 (🔍)
GCVE (CVE): GCVE-0-2024-10043
GCVE (VulDB): GCVE-100-288156
Entry
Created: 12/12/2024 15:03Updated: 07/12/2025 01:41
Changes: 12/12/2024 15:03 (66), 12/12/2024 16:50 (2), 07/12/2025 01:41 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.