First published: Fri Oct 11 2024(Updated: )
An issue was discovered in GitLab EE affecting all versions starting from 12.5 prior to 17.2.9, starting from 17.3, prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows running pipelines on arbitrary branches.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=12.5.0<17.2.9 | |
GitLab | >=12.5.0<17.2.9 | |
GitLab | >=17.3.0<17.3.5 | |
GitLab | >=17.3.0<17.3.5 | |
GitLab | >=17.4.0<17.4.2 | |
GitLab | >=17.4.0<17.4.2 |
Upgrade to versions 17.2.9, 17.3.5, 17.4.2 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-9164 is considered a critical vulnerability due to its potential to allow unauthorized execution of arbitrary pipeline code.
To mitigate CVE-2024-9164, upgrade your GitLab instance to versions later than 17.2.9, 17.3.5, or 17.4.2, depending on your current version.
CVE-2024-9164 affects GitLab EE and CE versions starting from 12.5 and before several specified versions ranging from 17.2.9 to 17.4.2.
CVE-2024-9164 enables the running of pipelines on arbitrary branches, which could lead to unauthorized access and potential data manipulation.
Yes, both GitLab Community Edition (CE) and GitLab Enterprise Edition (EE) versions are vulnerable under the specified conditions in CVE-2024-9164.