Maintainer impersonation via stale mirror identity
Published Jun 19, 2020 · Updated Aug 4, 2024
Improper authorization in GitLab EE affected releases allows remote authenticated users to retain limited maintainer actions. Removing a pull mirror leaves project.mirror_user assigned, and mirror-user validation accepts that stale identity when another maintainer creates a new pull mirror. A project maintainer can therefore bind a controlled repository to the former mirror user and preserve maintainer-authorized commit activity after losing project membership.
Summary
What happened
Improper authorization in GitLab EE affected releases allows remote authenticated users to retain limited maintainer actions. Removing a pull mirror leaves project.mirror_user assigned, and mirror-user validation accepts that stale identity when another maintainer creates a new pull mirror. A project maintainer can therefore bind a controlled repository to the former mirror user and preserve maintainer-authorized commit activity after losing project membership.
The record
- CVE
- CVE-2020-13263
- Published
- Jun 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=12.10, <12.10.7
- Affected versionversion=>=13.0, <13.0.1
- Affected versionversion=>=9.5, <12.9.8
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
Public exploit references
- GitLab issue 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