Project-owner pipeline execution via registry event fallback
Published Feb 13, 2025 · Updated Feb 13, 2025
Improper privilege management in GitLab CE/EE 17.1.0 through 17.5.2 allows remote authenticated users to run pipelines as project owners. During a deploy-token image push, ee/app/models/ee/container_registry/event.rb substitutes the project owner when the registry event lacks a user originator, and the scanning worker launches the resulting pipeline with that identity. Exploitation requires Maintainer access, an Ultimate project in a user namespace, an enabled container registry, and registry vulnerability scanning; successful jobs execute with the owner's CI/CD privileges.
Summary
What happened
Improper privilege management in GitLab CE/EE 17.1.0 through 17.5.2 allows remote authenticated users to run pipelines as project owners. During a deploy-token image push, ee/app/models/ee/container_registry/event.rb substitutes the project owner when the registry event lacks a user originator, and the scanning worker launches the resulting pipeline with that identity. Exploitation requires Maintainer access, an Ultimate project in a user namespace, an enabled container registry, and registry vulnerability scanning; successful jobs execute with the owner's CI/CD privileges.
The record
- CVE
- CVE-2024-8266
- Published
- Feb 13, 2025
- Updated
- Feb 13, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-250, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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.1 <17.6.0
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
- Container registry push reproduction stepsproof of concept · unverified
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