Unauthorized project access via unapplied group changes
Published Mar 13, 2020 · Updated Aug 4, 2024
Improper permission preservation in GitLab 12.7 through 12.8.1 allows remote attackers to retain project access after group changes. GitLab has not published the affected code locus; under an undisclosed group-related condition, it fails to apply a project authorization change. The required group configuration is undisclosed, and retained authorization permits access to project data after permissions should have changed.
Summary
What happened
Improper permission preservation in GitLab 12.7 through 12.8.1 allows remote attackers to retain project access after group changes. GitLab has not published the affected code locus; under an undisclosed group-related condition, it fails to apply a project authorization change. The required group configuration is undisclosed, and retained authorization permits access to project data after permissions should have changed.
The record
- CVE
- CVE-2020-10083
- Published
- Mar 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-281
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 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
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