Arbitrary-user pipeline execution via stop-action identity confusion
Published Sep 12, 2024 · Updated Sep 13, 2024
Authentication bypass in affected GitLab CE/EE releases allows remote authenticated users to trigger pipelines as arbitrary users. The environment stop-action path assigns the stop-action job owner's identity to a pipeline triggered by another user instead of using the triggering user's identity. Low-privilege access is required; affected branches are 8.14 through 17.1.6, 17.2 before 17.2.5, and 17.3 before 17.3.2.
Summary
What happened
Authentication bypass in affected GitLab CE/EE releases allows remote authenticated users to trigger pipelines as arbitrary users. The environment stop-action path assigns the stop-action job owner's identity to a pipeline triggered by another user instead of using the triggering user's identity. Low-privilege access is required; affected branches are 8.14 through 17.1.6, 17.2 before 17.2.5, and 17.3 before 17.3.2.
The record
- CVE
- CVE-2024-6678
- Published
- Sep 12, 2024
- Updated
- Sep 13, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-290, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 12, 2024CVE publishedPublication date reported by the CVE source.
- Sep 13, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.2 <17.2.5
- Affected versionversion=17.3 <17.3.2
- Affected versionversion=8.14 <17.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo