Security readout for executives and security teams
Plain-English summary
Affected GitLab EE versions allowed an attacker, in limited circumstances, to change the name or path of a public top-level group. That could disrupt access, confuse users, and damage integrity of project URLs or group identity. The issue is high severity, but the source bundle does not show active exploitation.
Executive priority
Treat this as a high-priority GitLab maintenance issue, especially where public groups support customer, partner, or developer workflows. It is not KEV-confirmed active exploitation, but unauthorized group identity changes could create operational disruption and trust impact.
Technical view
CVE-2023-3484 is an incorrect authorization issue in GitLab EE. A low-privileged attacker, with user interaction and high attack complexity, could alter a public top-level group name or path in certain situations. Affected ranges are 12.8 before 15.11.11, 16.0 before 16.0.7, and 16.1 before 16.1.2.
Likely exposure
Exposure is most likely in GitLab EE instances running the listed affected versions and hosting public top-level groups. Organizations without public top-level groups or already on fixed versions have lower likely exposure, based on the provided sources.
Exploitation context
The CVE is not listed as KEV, and the provided bundle does not cite active exploitation in the wild. The HackerOne reference is tagged for technical description, exploit, and permissions-required, so defenders should assume enough detail exists for validation without treating it as confirmed real-world exploitation.
Researcher notes
Focus validation on GitLab EE authorization behavior around public top-level group rename and path changes. The CVSS vector indicates network access, low privileges, user interaction, high complexity, and changed scope with high confidentiality, integrity, and availability impact.
Mitigation direction
- Upgrade GitLab EE to 15.11.11, 16.0.7, 16.1.2, or a later fixed release.
- Prioritize instances containing public top-level groups.
- Review vendor guidance from GitLab before applying temporary operational controls.
- Monitor public group name and path changes until remediation is complete.
Validation and detection
- Inventory GitLab EE versions across self-managed environments.
- Compare versions against affected ranges: 12.8-15.11.10, 16.0-16.0.6, and 16.1-16.1.1.
- Identify public top-level groups on affected instances.
- Review available audit history for unexpected group name or path changes.
- Confirm patched instances are no longer in the vulnerable version ranges.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-3484 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
- High
- CVSS
- 8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
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:C/C:H/I:H/A:H1.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #416773CVE reference · issue-tracking
- HackerOne Bug Bounty Report #2035687CVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.