Service degradation via runaway service-record creation
Published Mar 10, 2020 · Updated Aug 4, 2024
Uncontrolled resource consumption in GitLab CE and EE 11.11 through 12.0.2 allows remote authenticated users to exhaust server resources. Enabling certain instance-wide service templates repeatedly creates project service records, allowing the services table to grow by millions of rows and saturate Sidekiq CPU. Administrator privileges and explicit template enablement are required; the consequence is service degradation rather than data disclosure or modification.
Summary
What happened
Uncontrolled resource consumption in GitLab CE and EE 11.11 through 12.0.2 allows remote authenticated users to exhaust server resources. Enabling certain instance-wide service templates repeatedly creates project service records, allowing the services table to grow by millions of rows and saturate Sidekiq CPU. Administrator privileges and explicit template enablement are required; the consequence is service degradation rather than data disclosure or modification.
The record
- CVE
- CVE-2019-13007
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 10, 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.
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.
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