Unauthorized project deploy-key permission changes
Published Jun 9, 2020 · Updated Aug 4, 2024
Missing authorization in GitLab CE/EE 12.8 through 13.0.1 allows context-dependent attackers to alter project deploy-key permissions. GitLab identifies the affected locus as Project Deploy Keys but has not published the exact handler or missing authorization check. Exploitation requires conditions that GitLab has not publicly detailed and changes another user's deploy-key permissions, affecting repository access integrity.
Summary
What happened
Missing authorization in GitLab CE/EE 12.8 through 13.0.1 allows context-dependent attackers to alter project deploy-key permissions. GitLab identifies the affected locus as Project Deploy Keys but has not published the exact handler or missing authorization check. Exploitation requires conditions that GitLab has not publicly detailed and changes another user's deploy-key permissions, affecting repository access integrity.
The record
- CVE
- CVE-2020-13266
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 9, 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=>=12.8, <12.9.8
- Affected versionversion=>=13.0, <13.0.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
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