CVE-2024-8641: Privilege Context Switching Error in GitLab
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 CIJOBTOKEN to obtain a GitLab session token belonging to the victim.
Other sources
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 CIJOBTOKEN to obtain a GitLab session token belonging to the victim. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L, 6.7). It is now mitigated in the latest release and is assigned CVE-2024-8641.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-8641?
CVE-2024-8641 has a high severity rating due to the potential for unauthorized access to user sessions.
How do I fix CVE-2024-8641?
To fix CVE-2024-8641, upgrade GitLab to version 17.1.7 or later, 17.2.5 or later, or 17.3.2 or later.
What versions are affected by CVE-2024-8641?
CVE-2024-8641 affects all GitLab versions starting from 13.7 up to but not including 17.1.7, 17.2.5, and 17.3.2.
Who can exploit CVE-2024-8641?
An attacker with a victim's CI_JOB_TOKEN could exploit CVE-2024-8641 to obtain a session token.
Is there a workaround for CVE-2024-8641?
There is no public workaround for CVE-2024-8641; upgrading to a fixed version is the only mitigation.