Protected pipeline status overwrite via unchecked commit API
Published Feb 5, 2020 · Updated Aug 4, 2024
Incorrect permissions in GitLab EE 8.8 through 12.7.2 allow remote authenticated users to overwrite protected-branch pipeline status. The commit-status API accepts an existing stage name and overwrites the aggregate pipeline status without checking whether the commit belongs to a protected ref. Project Developer access is sufficient to falsify deployment results or satisfy the pipeline-must-succeed merge gate.
Summary
What happened
Incorrect permissions in GitLab EE 8.8 through 12.7.2 allow remote authenticated users to overwrite protected-branch pipeline status. The commit-status API accepts an existing stage name and overwrites the aggregate pipeline status without checking whether the commit belongs to a protected ref. Project Developer access is sufficient to falsify deployment results or satisfy the pipeline-must-succeed merge gate.
The record
- CVE
- CVE-2020-7977
- Published
- Feb 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 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
- Protected-pipeline status overwrite 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