CVE-2023-5963: Allocation of Resources Without Limits or Throttling in GitLab
An issue has been discovered in GitLab EE with Advanced Search affecting all versions from 13.9 to 16.3.6, 16.4 prior to 16.4.2 and 16.5 prior to 16.5.1 that could allow a denial of service in the Advanced Search function by chaining too many syntax operators.
Security readout for executives and security teams
Plain-English summary
CVE-2023-5963 is a low-severity denial-of-service issue in GitLab EE Advanced Search. An authenticated user could overload the search function by using excessive search syntax operators. The reported impact is limited availability loss, not data theft or tampering.
Executive priority
Treat this as a routine availability fix unless Advanced Search is business-critical or exposed to many users. Prioritize patching during normal maintenance, with faster action for large shared GitLab environments where search disruption would affect developer productivity.
Technical view
GitLab EE Advanced Search lacks sufficient resource limiting for chained syntax operators. Affected versions are reported as 13.9 through 16.3.6, 16.4 before 16.4.2, and 16.5 before 16.5.1. CVSS is 3.1: network exploitable, high attack complexity, low privileges required, and low availability impact.
Likely exposure
Exposure is limited to GitLab Enterprise Edition deployments using Advanced Search on affected versions. The attacker needs a valid low-privileged account. GitLab instances without Advanced Search, non-EE deployments, or versions outside the affected ranges are less likely to be exposed based on provided sources.
Exploitation context
No source provided indicates active exploitation, and this CVE is not listed as KEV. The attack path involves abusing Advanced Search syntax complexity, but public sources describe only denial of service, not code execution, privilege escalation, or data compromise.
Researcher notes
The CVSS vector is AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L. The weakness maps to CWE-770, allocation of resources without limits or throttling. Evidence is limited to the CVE data and GitLab issue reference; no exploit status or broader impact is supported.
Mitigation direction
Inventory GitLab EE instances and identify whether Advanced Search is enabled.
Upgrade affected 16.4 deployments to 16.4.2 or later.
Upgrade affected 16.5 deployments to 16.5.1 or later.
For 13.9 through 16.3.6, check current GitLab vendor guidance.
Monitor Advanced Search resource usage and error rates until remediation is complete.
Validation and detection
Confirm GitLab edition, version, and Advanced Search status.
Compare versions against the affected ranges in the CVE record.
Review GitLab advisory or issue tracker for remediation guidance.
Check monitoring for Advanced Search latency, failures, or resource spikes.
Verify upgraded instances report a non-affected version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.