Unauthorized visibility changes via inconsistent numeric coercion
Published Aug 5, 2022 · Updated Aug 3, 2024
Incorrect authorization in GitLab CE/EE 15.0.4 and earlier, 15.1.0 through 15.1.3, and 15.2.0 allows remote authenticated users to change visibility. UpdateVisibilityLevel validates a coerced visibility value before the submitted string is later converted with to_i, so 20r compares as private but is saved as public. Maintainer access to a target project or group is required, and a successful request can make that private target public.
Summary
What happened
Incorrect authorization in GitLab CE/EE 15.0.4 and earlier, 15.1.0 through 15.1.3, and 15.2.0 allows remote authenticated users to change visibility. UpdateVisibilityLevel validates a coerced visibility value before the submitted string is later converted with to_i, so 20r compares as private but is saved as public. Maintainer access to a target project or group is required, and a successful request can make that private target public.
The record
- CVE
- CVE-2022-2456
- Published
- Aug 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 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=>=0.0, <15.0.5
- Affected versionversion=>=15.1, <15.1.4
- Affected versionversion=>=15.2, <15.2.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.
Public exploit references
- GitLab issue 359910 reproduction procedureproof of concept · demonstrated
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