Approval-policy bypass via unauthorized GraphQL deletion
Published Jun 26, 2024 · Updated Aug 29, 2024
Improper access control in GitLab CE/EE allows remote authenticated users to delete merge request approval policies through GraphQL. The GraphQL authorization path accepts project-maintainer privileges for deletion of a group-controlled policy from the project context. Exploitation requires project-maintainer access; affected releases span 16.10.0 through 16.11.4, 17.0.0 through 17.0.2, and 17.1.0, and deletion removes the merge gate.
Summary
What happened
Improper access control in GitLab CE/EE allows remote authenticated users to delete merge request approval policies through GraphQL. The GraphQL authorization path accepts project-maintainer privileges for deletion of a group-controlled policy from the project context. Exploitation requires project-maintainer access; affected releases span 16.10.0 through 16.11.4, 17.0.0 through 17.0.2, and 17.1.0, and deletion removes the merge gate.
The record
- CVE
- CVE-2024-5430
- Published
- Jun 26, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-284, T1562.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=16.10 <16.11.5
- Affected versionversion=17.0 <17.0.3
- Affected versionversion=17.1 <17.1.1
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
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