Sensitive data exposure via overbroad token scopes
Published Nov 26, 2024 · Updated Nov 30, 2024
Incorrect authorization in GitLab CE/EE allows remote authenticated users to access sensitive data through certain API endpoints. In versions 16.9.8 through 17.4.4, 17.5 through 17.5.2, and 17.6, token scopes are applied too broadly when those endpoints authorize requests; GitLab has not publicly identified the endpoints or validation logic. A high-privilege token is required, and the documented impact is unauthorized data access and modification without service interruption.
Summary
What happened
Incorrect authorization in GitLab CE/EE allows remote authenticated users to access sensitive data through certain API endpoints. In versions 16.9.8 through 17.4.4, 17.5 through 17.5.2, and 17.6, token scopes are applied too broadly when those endpoints authorize requests; GitLab has not publicly identified the endpoints or validation logic. A high-privilege token is required, and the documented impact is unauthorized data access and modification without service interruption.
The record
- CVE
- CVE-2024-11669
- Published
- Nov 26, 2024
- Updated
- Nov 30, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1550.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 30, 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.9.8 <17.4.5
- Affected versionversion=17.5 <17.5.3
- Affected versionversion=17.6 <17.6.1
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