Security readout for executives and security teams
Plain-English summary
CVE-2023-4912 is a low-severity GitLab EE issue where specially crafted Mermaid diagram content could make a user's browser or client-side view become unavailable. It does not indicate data theft or server takeover. Business impact is mainly localized disruption for users who view malicious content.
Executive priority
Treat this as routine patch management unless affected GitLab instances are heavily shared or difficult to update. It has low business urgency compared with server-side compromise issues, but should still be closed during the next maintenance cycle.
Technical view
GitLab EE versions from 10.5 before 16.4.3, 16.5 before 16.5.3, and 16.6 before 16.6.1 are affected. The flaw is CWE-770, allocation of resources without limits or throttling, triggered by crafted Mermaid diagram input. CVSS 3.1 is 2.6 with low availability impact.
Likely exposure
Exposure is most likely on self-managed GitLab EE instances in the affected version ranges where authenticated users can create or submit Mermaid diagram content for others to view.
Exploitation context
The source bundle does not show confirmed active exploitation, and KEV is false. Public detail is limited because the GitLab issue and HackerOne report are marked permission-required. Exploitation requires privileges and user interaction, with impact limited to client-side denial of service.
Researcher notes
The available evidence supports a client-side availability issue only. Do not infer confidentiality or integrity impact. Because detailed references require permissions, validation should focus on version exposure, Mermaid rendering paths, and confirmation against GitLab's fixed release boundaries.
Mitigation direction
- Upgrade affected GitLab EE instances to 16.4.3, 16.5.3, 16.6.1, or later.
- Check current GitLab vendor guidance before applying any temporary workaround.
- Prioritize internet-facing or broadly used internal GitLab instances first.
- Communicate potential browser disruption risk to GitLab administrators and support teams.
Validation and detection
- Inventory GitLab EE versions across self-managed instances.
- Confirm no instance remains in the affected version ranges.
- Identify projects or workflows that allow Mermaid diagram rendering.
- Review helpdesk or monitoring data for unusual client-side GitLab rendering failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2023-4912 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L1.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
2.6LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #424882CVE reference · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2137421CVE reference · technical-description, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.