Forced merge-request approval via SAML-session CSRF
Published May 9, 2024 · Updated Aug 29, 2024
Cross-site request forgery in GitLab EE allows remote authenticated users to force merge-request approval through a victim's active SAML session. Public vendor material does not identify the request handler or explain which CSRF validation operation fails on the merge-request approval path. Exploitation requires attacker authentication, a victim with an active SAML session, and user interaction; the resulting action records an approval as the victim.
Summary
What happened
Cross-site request forgery in GitLab EE allows remote authenticated users to force merge-request approval through a victim's active SAML session. Public vendor material does not identify the request handler or explain which CSRF validation operation fails on the merge-request approval path. Exploitation requires attacker authentication, a victim with an active SAML session, and user interaction; the resulting action records an approval as the victim.
The record
- CVE
- CVE-2024-4597
- Published
- May 9, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 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.10.5
- Affected versionversion=16.11 <16.11.2
- Affected versionversion=16.7 <16.9.7
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