CVE-2024-5655: Improper Access Control in GitLab
First published: Wed Jun 26 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows an attacker to trigger a pipeline as another user under certain circumstances.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=15.8.0<16.11.5 | |
| GitLab | >=15.8.0<16.11.5 | |
| GitLab | >=17.0.0<17.0.3 | |
| GitLab | >=17.0.0<17.0.3 | |
| GitLab | =17.1.0 | |
| GitLab | =17.1.0 |
Remedy
Upgrade to versions 17.1.1, 17.0.3, 16.11.5 or above.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://www.bleepingcomputer.com/news/security/critical-gitlab-bug-lets-attackers-run-pipelines-as-any-user/
- https://gitlab.com/gitlab-org/gitlab/-/issues/465862
- https://hackerone.com/reports/2536320
- https://www.bleepingcomputer.com/news/security/gitlab-warns-of-critical-bug-that-lets-attackers-run-pipelines-as-an-arbitrary-user/
- https://www.bleepingcomputer.com/news/security/gitlab-warns-of-critical-pipeline-execution-vulnerability/
- https://www.bleepingcomputer.com/news/security/gitlab-warns-of-critical-arbitrary-branch-pipeline-execution-flaw/
Frequently Asked Questions
What is the severity of CVE-2024-5655?
CVE-2024-5655 has been classified as a critical vulnerability due to its potential to allow unauthorized users to trigger pipelines.
How do I fix CVE-2024-5655?
To fix CVE-2024-5655, upgrade GitLab to version 16.11.5 or later, or 17.0.3 or later, or 17.1.1 or later.
Which versions are affected by CVE-2024-5655?
CVE-2024-5655 affects GitLab CE/EE versions from 15.8 up to 16.11.4, from 17.0 up to 17.0.2, and the exact version 17.1.0.
What is the impact of CVE-2024-5655?
The impact of CVE-2024-5655 allows attackers to trigger pipelines as another user, which can lead to unauthorized actions within the GitLab environment.
Is there a workaround for CVE-2024-5655?
There are currently no documented workarounds for CVE-2024-5655, and upgrading is the recommended action.
- agent/remedy
- agent/weakness
- agent/title
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- collector/bleeping-computer
- source/BleepingComputer
- alias/CVE-2024-5655
- agent/severity
- agent/softwarecombine
- alias/CVE-2024-6385
- alias/CVE-2024-4835
- alias/CVE-2023-7028
- collector/epss-latest
- source/FIRST
- agent/epss
- alias/CVE-2024-6678
- alias/CVE-2023-5009
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- alias/CVE-2024-9164
- agent/references
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/15.8.0
- version/gitlab/17.0.0
- version/gitlab/17.1.0