GitLab Community Edition/Enterprise Edition up to 17.1.6/17.2.4/17.3.1 Session Token CI_JOB_TOKEN privilege context switching
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 17.1.6/17.2.4/17.3.1. This issue affects some unknown processing of the component Session Token Handler. The manipulation of the argument CI_JOB_TOKEN leads to privilege context switching. This vulnerability is referenced as CVE-2024-8641. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.1.6/17.2.4/17.3.1. It has been rated as problematic. This issue affects some unknown processing of the component Session Token Handler. The manipulation of the argument CI_JOB_TOKEN with an unknown input leads to a privilege context switching vulnerability. Using CWE to declare the problem leads to CWE-270. The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. It may have been possible for an attacker with a victim's CI_JOB_TOKEN to obtain a GitLab session token belonging to the victim.
The weakness was published by yvvdwf as 471954. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2024-8641 since 09/10/2024. The exploitation is known to be difficult. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 17.1.7, 17.2.5 or 17.3.2 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.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.7
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: Privilege context switchingCWE: CWE-270 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.1.7/17.2.5/17.3.2
Timeline
09/10/2024 🔍09/12/2024 🔍
09/12/2024 🔍
03/10/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 471954
Researcher: yvvdwf
Status: Confirmed
CVE: CVE-2024-8641 (🔍)
GCVE (CVE): GCVE-0-2024-8641
GCVE (VulDB): GCVE-100-277325
Entry
Created: 09/12/2024 21:29Updated: 03/10/2025 12:56
Changes: 09/12/2024 21:29 (67), 03/10/2025 12:56 (3)
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.