Prometheus service interruption via malformed HTTP methods
Published Jan 15, 2021 · Updated Aug 3, 2024
Uncontrolled resource consumption in GitLab 13.7.0 through 13.7.1 allows remote attackers to interrupt Prometheus via a malformed HTTP method. GitLab identifies Prometheus request handling and the attacker-controlled method as the trigger but has not published the resource-consumption operation. No authentication or user interaction is required, and the reported consequence is limited to Prometheus availability.
Summary
What happened
Uncontrolled resource consumption in GitLab 13.7.0 through 13.7.1 allows remote attackers to interrupt Prometheus via a malformed HTTP method. GitLab identifies Prometheus request handling and the attacker-controlled method as the trigger but has not published the resource-consumption operation. No authentication or user interaction is required, and the reported consequence is limited to Prometheus availability.
The record
- CVE
- CVE-2021-22166
- Published
- Jan 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 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=>=13.7, <13.7.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