Container image read and write via blocked-state bypass
Published Mar 27, 2020 · Updated Aug 4, 2024
Incorrect authorization in GitLab EE/CE 8.11 through 12.9.1 allows blocked remote authenticated users to pull or push container images. The container registry authorization flow grants pull and push access without enforcing the account's blocked state. A blocked account with valid registry credentials can therefore read existing images or write replacement images in previously accessible repositories.
Summary
What happened
Incorrect authorization in GitLab EE/CE 8.11 through 12.9.1 allows blocked remote authenticated users to pull or push container images. The container registry authorization flow grants pull and push access without enforcing the account's blocked state. A blocked account with valid registry credentials can therefore read existing images or write replacement images in previously accessible repositories.
The record
- CVE
- CVE-2020-10952
- Published
- Mar 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 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.
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