First published: Thu Sep 12 2024(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=13.7.0<17.1.7 | |
GitLab | >=13.7.0<17.1.7 | |
GitLab | >=17.2.0<17.2.5 | |
GitLab | >=17.2.0<17.2.5 | |
GitLab | >=17.3.0<17.3.2 | |
GitLab | >=17.3.0<17.3.2 |
Upgrade to version 17.1.7, 17.2.5 or 17.3.2
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8641 has a high severity rating due to the potential for unauthorized access to user sessions.
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.
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.
An attacker with a victim's CI_JOB_TOKEN could exploit CVE-2024-8641 to obtain a session token.
There is no public workaround for CVE-2024-8641; upgrading to a fixed version is the only mitigation.