Cross-group registry disclosure via stale namespace reuse
Published Feb 17, 2020 · Updated Aug 4, 2024
Improper access control in GitLab Enterprise 12.0.0-pre allows remote authenticated users to read other groups' container images. Changing a group path leaves its registry images in the old namespace, which a different user can reclaim by creating matching group and project paths. Access requires a GitLab account and reuse of the abandoned paths, exposing images from the prior private project.
Summary
What happened
Improper access control in GitLab Enterprise 12.0.0-pre allows remote authenticated users to read other groups' container images. Changing a group path leaves its registry images in the old namespace, which a different user can reclaim by creating matching group and project paths. Access requires a GitLab account and reuse of the abandoned paths, exposing images from the prior private project.
The record
- CVE
- CVE-2019-12825
- Published
- Feb 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-922, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 17, 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
- Cross-group container-registry access reproductionproof 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