Reporter-level issue management via missing authorization check
Published Jul 1, 2022 · Updated Aug 3, 2024
Improper authorization in GitLab EE/CE allows remote authenticated users with Reporter access to manage error-tracking issues. The affected error-tracking path fails to enforce project-level authorization before permitting issue-management actions. A Reporter can cross the intended authorization boundary when error tracking is configured; affected releases are 14.8 through 14.10.4, 15.0 through 15.0.3, and 15.1.0.
Summary
What happened
Improper authorization in GitLab EE/CE allows remote authenticated users with Reporter access to manage error-tracking issues. The affected error-tracking path fails to enforce project-level authorization before permitting issue-management actions. A Reporter can cross the intended authorization boundary when error tracking is configured; affected releases are 14.8 through 14.10.4, 15.0 through 15.0.3, and 15.1.0.
The record
- CVE
- CVE-2022-2244
- Published
- Jul 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.8, <14.10.5
- Affected versionversion=>=15.0, <15.0.4
- Affected versionversion=>=15.1, <15.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
No sourced classifications are available.
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