Pipeline impersonation via unrotated trigger tokens
Published Jan 28, 2020 · Updated Aug 4, 2024
Privilege escalation in GitLab CE/EE 9.0 and later allows remote authenticated users to run pipelines as a new token owner. Changing ownership reassigns the trigger token without rotating its secret, and the pipeline API continues accepting the value known by the former owner. Exploitation requires prior knowledge of that token and permits pipeline execution under the new owner's identity.
Summary
What happened
Privilege escalation in GitLab CE/EE 9.0 and later allows remote authenticated users to run pipelines as a new token owner. Changing ownership reassigns the trigger token without rotating its secret, and the pipeline API continues accepting the value known by the former owner. Exploitation requires prior knowledge of that token and permits pipeline execution under the new owner's identity.
The record
- CVE
- CVE-2019-5462
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613, CAPEC-233, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Trigger-token ownership-change reproductionproof of concept · 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