External-user snippet creation via missing authorization check
Published Apr 29, 2020 · Updated Aug 4, 2024
Authorization bypass in GitLab 12.6 through 12.9 allows remote authenticated users marked external to create personal snippets through the API. The personal-snippet API failed to check the create_personal_snippet ability before accepting the create request. An account classified as external is required, and the bypass grants only prohibited personal-snippet creation.
Summary
What happened
Authorization bypass in GitLab 12.6 through 12.9 allows remote authenticated users marked external to create personal snippets through the API. The personal-snippet API failed to check the create_personal_snippet ability before accepting the create request. An account classified as external is required, and the bypass grants only prohibited personal-snippet creation.
The record
- CVE
- CVE-2020-12275
- Published
- Apr 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 2020CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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