An issue has been discovered in GitLab affecting all versions starting from 10.6 before 16.1.5, all versions starting from 16.2 before 16.2.5, all versions starting from 16.3 before 16.3.1 in which any user can read limited information about any project's imports.
Security readout for executives and security teams
Plain-English summary
GitLab disclosed an authorization flaw that could let any authenticated user see limited information about any project's imports. This is not described as full project access, code theft, or service disruption, but it may expose sensitive operational metadata in affected GitLab deployments.
Executive priority
Treat this as a moderate-priority information disclosure issue. Remediate during the next regular security maintenance window, sooner for internet-facing or multi-tenant GitLab environments with sensitive private projects.
Technical view
CVE-2023-4630 is a CWE-862 missing authorization issue in GitLab. Affected ranges are 10.6 before 16.1.5, 16.2 before 16.2.5, and 16.3 before 16.3.1. The CVSS 3.1 score is 5.0, with low confidentiality impact and no integrity or availability impact.
Likely exposure
Exposure is limited to GitLab instances running the affected version ranges. The issue requires a user account, so externally reachable self-managed GitLab instances with broad account access deserve attention.
Exploitation context
The provided sources do not show CISA KEV listing or evidence of active exploitation. The issue is network reachable, low complexity, and requires low privileges, but the disclosed impact is limited information disclosure about project imports.
Researcher notes
The record identifies missing authorization around project import information, not broader repository access. Public detail is limited in the supplied bundle, so avoid assuming data scope beyond limited import information unless vendor issue details confirm it.
Mitigation direction
Inventory all GitLab instances and record exact versions.
Upgrade affected instances to 16.1.5, 16.2.5, 16.3.1, or later.
Review GitLab Issue #415117 for vendor-specific guidance.
Limit unnecessary GitLab user access while remediation is pending.
Assess whether project import metadata could reveal sensitive business information.
Validation and detection
Confirm no GitLab instance remains in the affected version ranges.
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 · medium confidence lookup
CWE-862: 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.
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-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.