Allocation of Resources Without Limits or Throttling in GitLab
GitLab · GitLab
GitLab CE/EE, the Issue description handling in GraphQL, lacks length validation, so large Issue descriptions can be created and processed without limit. An authenticated attacker with network access can create a large Issue description via GraphQL and, by repeatedly requesting it, saturate CPU usage (a denial-of-service condition), with no user interaction or special configuration required.
A lack of length validation in GitLab CE/EE affecting all versions from 8.3 before 15.10.8, 15.11 before 15.11.7, and 16.0 before 16.0.2 allows an authenticated attacker to create a large Issue description via GraphQL which, when repeatedly requested, saturates CPU usage.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 6 Jun 2023. No public exploit code or confirmed exploitation is recorded.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.