First published: Thu Sep 12 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, which allows an attacker to trigger a pipeline as an arbitrary user under certain circumstances.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.14.0<17.1.7 | |
GitLab | >=8.14.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 versions 17.1.7, 17.2.5, 17.3.2 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-6678 is classified as a critical vulnerability affecting GitLab versions from 8.14 up to 17.1.7, and from 17.2.0 up to 17.2.5 and 17.3.0 up to 17.3.2.
To mitigate CVE-2024-6678, upgrade GitLab to versions 17.1.7, 17.2.5, or 17.3.2 or later.
If exploited, CVE-2024-6678 allows an attacker to trigger a pipeline as an arbitrary user.
CVE-2024-6678 affects GitLab CE/EE versions from 8.14 to 17.1.7, 17.2.0 to 17.2.5, and 17.3.0 to 17.3.2.
No, CVE-2024-6678 affects both GitLab Community Edition (CE) and Enterprise Edition (EE).