Privilege escalation via cross-model memoization key collision
Published Dec 13, 2021 · Updated Aug 4, 2024
Improper access control in GitLab CE/EE before 14.3.6, 14.4 through 14.4.3, and 14.5 through 14.5.1 allows authenticated users to gain privileges. BulkMemberAccessLoad reuses a SafeRequestStore access-level key across projects and groups with the same numeric ID, causing one object's cached authorization to govern the other. Exploitation requires matching project and group IDs and both authorization checks in one request; documented GraphQL reads can cross access boundaries.
Summary
What happened
Improper access control in GitLab CE/EE before 14.3.6, 14.4 through 14.4.3, and 14.5 through 14.5.1 allows authenticated users to gain privileges. BulkMemberAccessLoad reuses a SafeRequestStore access-level key across projects and groups with the same numeric ID, causing one object's cached authorization to govern the other. Exploitation requires matching project and group IDs and both authorization checks in one request; documented GraphQL reads can cross access boundaries.
The record
- CVE
- CVE-2021-39937
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-269, T1068
- 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=>=0.0, <14.3.6
- Affected versionversion=>=14.4, <14.4.4
- Affected versionversion=>=14.5, <14.5.2
What conditions does exploitation require?
What is affected?
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