Unauthorized merge request approval via stale permissions
Published Dec 13, 2021 · Updated Aug 4, 2024
GitLab 9.4 through 14.3.5, 14.4 through 14.4.3, and 14.5 through 14.5.1 allow remote authenticated users to approve merge requests after revocation. The approval API invokes MergeRequests::ApprovalService after a policy equates approval permission with update permission, leaving demoted authors authorized. A valid personal access token and prior merge-request authorship are required; successful requests change approval state and disclose private merge-request details.
Summary
What happened
GitLab 9.4 through 14.3.5, 14.4 through 14.4.3, and 14.5 through 14.5.1 allow remote authenticated users to approve merge requests after revocation. The approval API invokes MergeRequests::ApprovalService after a policy equates approval permission with update permission, leaving demoted authors authorized. A valid personal access token and prior merge-request authorship are required; successful requests change approval state and disclose private merge-request details.
The record
- CVE
- CVE-2021-39945
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=14.4, <14.4.4
- Affected versionversion=>=14.5, <14.5.2
- Affected versionversion=>=9.4, <14.3.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
Public exploit references
- GitLab issue reproduction stepsproof 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