Internal repository disclosure via shared object pools
Published Apr 2, 2021 · Updated Aug 3, 2024
Improper access control in affected GitLab CE/EE releases allows remote attackers to read internal repository data through a public fork. A public fork remains linked to its object pool after the source becomes internal, and housekeeping copies new internal objects into that pool. Anonymous access requires the object ID because affected refs are not advertised; successful fetches disclose only the referenced repository objects.
Summary
What happened
Improper access control in affected GitLab CE/EE releases allows remote attackers to read internal repository data through a public fork. A public fork remains linked to its object pool after the source becomes internal, and housekeeping copies new internal objects into that pool. Anonymous access requires the object ID because affected refs are not advertised; successful fetches disclose only the referenced repository objects.
The record
- CVE
- CVE-2021-22200
- Published
- Apr 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2021CVE 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=>=12.6, <13.8.7
- Affected versionversion=>=13.10, <13.10.1
- Affected versionversion=>=13.9, <13.9.5
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 object-pool disclosure 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