GitLab Enterprise Edition up to 16.3 Protected Branch exposure of sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Enterprise Edition up to 16.3. It has been rated as problematic. This affects an unknown function of the component Protected Branch Handler. The manipulation leads to exposure of sensitive information. This vulnerability is uniquely identified as CVE-2023-3441. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, has been found in GitLab Enterprise Edition up to 16.3. This issue affects an unknown function of the component Protected Branch Handler. The manipulation with an unknown input leads to a exposure of sensitive information vulnerability. Using CWE to declare the problem leads to CWE-213. The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue has been discovered in GitLab EE/CE affecting all versions starting from 8.0 before 16.4. The product did not sufficiently warn about security implications of granting merge rights to protected branches.
The weakness was disclosed by samuellg as 416482. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2023-3441 since 06/28/2023. The exploitation is known to be difficult. The attack may be initiated remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 16.4 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.6
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: Exposure of sensitive informationCWE: CWE-213 / CWE-200 / CWE-284
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Enterprise Edition 16.4
Timeline
06/28/2023 🔍10/01/2024 🔍
10/01/2024 🔍
10/02/2024 🔍
Sources
Vendor: gitlab.comAdvisory: 416482
Researcher: samuellg
Status: Confirmed
CVE: CVE-2023-3441 (🔍)
GCVE (CVE): GCVE-0-2023-3441
GCVE (VulDB): GCVE-100-278957
Entry
Created: 10/01/2024 13:11Updated: 10/02/2024 03:52
Changes: 10/01/2024 13:11 (66), 10/02/2024 03:52 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.