Service interruption via dependency proxy purge requests
Published Jan 18, 2022 · Updated Aug 2, 2024
Denial of service in affected GitLab releases allows remote authenticated users to interrupt service via package deletion requests. The dependency proxy purge API marks cached manifests and blobs expired but does not reliably enqueue the limited-capacity cleanup workers that remove them. Exploitation requires permission to purge a group's dependency proxy cache; published sources do not identify the exact failure mode that interrupts service.
Summary
What happened
Denial of service in affected GitLab releases allows remote authenticated users to interrupt service via package deletion requests. The dependency proxy purge API marks cached manifests and blobs expired but does not reliably enqueue the limited-capacity cleanup workers that remove them. Exploitation requires permission to purge a group's dependency proxy cache; published sources do not identify the exact failure mode that interrupts service.
The record
- CVE
- CVE-2022-0151
- Published
- Jan 18, 2022
- Updated
- Aug 2, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1499
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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, <14.4.5
- Affected versionversion=>=14.5.0, <14.5.3
- Affected versionversion=>=14.6.0, <14.6.2
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