Service degradation via catastrophic regex backtracking
Published Apr 4, 2022 · Updated Aug 2, 2024
ReDoS in GitLab before 14.7.7, 14.8.5, or 14.9.2 allows remote authenticated users to exhaust CPU through the release-link API. The API's release-asset link update path applies a regex check whose exponential backtracking is triggered by crafted user-controlled values. An authenticated user able to update a release link can drive sustained high CPU usage, degrading service availability without reading or modifying data.
Summary
What happened
ReDoS in GitLab before 14.7.7, 14.8.5, or 14.9.2 allows remote authenticated users to exhaust CPU through the release-link API. The API's release-asset link update path applies a regex check whose exponential backtracking is triggered by crafted user-controlled values. An authenticated user able to update a release link can drive sustained high CPU usage, degrading service availability without reading or modifying data.
The record
- CVE
- CVE-2022-1100
- Published
- Apr 4, 2022
- Updated
- Aug 2, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-772, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 4, 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=>=13.1, <14.7.7
- Affected versionversion=>=14.8, <14.8.5
- Affected versionversion=>=14.9, <14.9.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