Authenticated cross-user pipeline execution via schedule editing
Published May 11, 2022 · Updated Aug 3, 2024
Improper authorization in affected GitLab releases allows remote authenticated users to run scheduled pipelines as another user. The schedule edit path failed to require nonowners to take ownership before changing a schedule, so later jobs retained the owner's permissions. Maintainer-level access and interaction by the schedule owner are required; successful abuse exposes resources available to that owner and alters pipeline execution.
Summary
What happened
Improper authorization in affected GitLab releases allows remote authenticated users to run scheduled pipelines as another user. The schedule edit path failed to require nonowners to take ownership before changing a schedule, so later jobs retained the owner's permissions. Maintainer-level access and interaction by the schedule owner are required; successful abuse exposes resources available to that owner and alters pipeline execution.
The record
- CVE
- CVE-2022-1460
- Published
- May 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 11, 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=>=14.10, <14.10.1
- Affected versionversion=>=14.9, <14.9.4
- Affected versionversion=>=9.2, <14.8.6
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
No sourced classifications are available.
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