Unauthorized deploy-token creation via push-rule permission
Published Jul 11, 2024 · Updated Aug 29, 2024
Authorization bypass in GitLab CE/EE 17.0 through 17.0.3 and 17.1 through 17.1.1 allows remote authenticated users to create deploy tokens. The project deploy-token creation endpoint treats the admin_push_rules custom-role ability as sufficient authorization, although that ability is intended only to manage push rules. A Guest assigned that ability can mint tokens granting read and write access to project repositories, packages, and registry images.
Summary
What happened
Authorization bypass in GitLab CE/EE 17.0 through 17.0.3 and 17.1 through 17.1.1 allows remote authenticated users to create deploy tokens. The project deploy-token creation endpoint treats the admin_push_rules custom-role ability as sufficient authorization, although that ability is intended only to manage push rules. A Guest assigned that ability can mint tokens granting read and write access to project repositories, packages, and registry images.
The record
- CVE
- CVE-2024-5470
- Published
- Jul 11, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-284, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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.0 <17.0.4
- Affected versionversion=17.1 <17.1.2
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- GitLab project deploy-token reproduction requestfunctional · demonstrated
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