Service interruption via crafted Markdown ReDoS
Published May 9, 2024 · Updated Oct 3, 2024
ReDoS in GitLab CE/EE before 16.9.7, 16.10 before 16.10.5, and 16.11 before 16.11.2 allows remote authenticated users to interrupt service. GitLab identifies the locus as the Markdown render pipeline but has not published the affected regular expression or its exact matching operation. Low-privileged access is required; crafted Markdown drives excessive CPU work and can make the self-managed service unavailable.
Summary
What happened
ReDoS in GitLab CE/EE before 16.9.7, 16.10 before 16.10.5, and 16.11 before 16.11.2 allows remote authenticated users to interrupt service. GitLab identifies the locus as the Markdown render pipeline but has not published the affected regular expression or its exact matching operation. Low-privileged access is required; crafted Markdown drives excessive CPU work and can make the self-managed service unavailable.
The record
- CVE
- CVE-2024-2651
- Published
- May 9, 2024
- Updated
- Oct 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-1333, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 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=0.0 <16.9.7
- Affected versionversion=16.10 <16.10.5
- Affected versionversion=16.11 <16.11.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