Pipeline execution via trigger-token IP allowlist bypass
Published Jun 6, 2022 · Updated Aug 3, 2024
Incorrect authorization in GitLab EE allows remote authenticated users with a valid Project Trigger Token to run pipelines from blocked IPs. The pipeline trigger API accepts the token without applying the configured group IP allowlist to the request source. Exploitation requires both the token and an IP-restricted project, and the bounded consequence is unauthorized pipeline execution.
Summary
What happened
Incorrect authorization in GitLab EE allows remote authenticated users with a valid Project Trigger Token to run pipelines from blocked IPs. The pipeline trigger API accepts the token without applying the configured group IP allowlist to the request source. Exploitation requires both the token and an IP-restricted project, and the bounded consequence is unauthorized pipeline execution.
The record
- CVE
- CVE-2022-1935
- Published
- Jun 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=>=12.0.0, <14.9.5
- Affected versionversion=>=14.10.0, <14.10.4
- Affected versionversion=>=15.0.0, <15.0.1
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
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