An issue has been discovered in GitLab affecting all versions starting from 13.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. It was possible for users to access composer packages on public projects that have package registry disabled in the project settings.
Security readout for executives and security teams
Plain-English summary
CVE-2023-3964 is a GitLab authorization flaw. In affected versions, a user could access Composer packages in public projects even when the project’s package registry was disabled. The business impact is limited data exposure, not system takeover. Prioritize affected public projects that use Composer packages or rely on registry-disablement as an access control.
Executive priority
Treat as a targeted, moderate-priority confidentiality issue. It is unlikely to cause service disruption or direct compromise, but it can expose package artifacts where teams expected registry access to be disabled.
Technical view
GitLab versions from 13.2 before 16.4.3, 16.5 before 16.5.3, and 16.6 before 16.6.1 are affected. The issue is CWE-863 incorrect authorization with CVSS 4.3: network reachable, low complexity, low privileges required, no user interaction, confidentiality impact only.
Likely exposure
Exposure is most relevant to GitLab deployments with public projects containing Composer packages where the package registry is disabled in project settings. Private projects are not identified as affected in the provided description.
Exploitation context
The vulnerability requires a user account but no user interaction. Sources do not indicate CISA KEV listing or confirmed active exploitation. The cited HackerOne report is a technical bug bounty reference, not evidence of active attacks.
Researcher notes
The core issue is authorization bypass of project package registry settings for Composer packages on public projects. Avoid assuming broader package types or private project impact unless vendor sources confirm it. The CVSS vector indicates low-privileged access is required.
Mitigation direction
Upgrade affected GitLab versions to 16.4.3, 16.5.3, 16.6.1, or later supported releases.
Identify public projects with Composer packages and disabled package registries.
Review GitLab vendor guidance for any additional version-specific remediation.
Restrict sensitive package publication in public projects until patched.
Validation and detection
Inventory GitLab versions against the affected version ranges.
Check for public projects using Composer packages with package registry disabled.
Confirm upgraded instances enforce disabled package registry settings as intended.
Review package access logs for unexpected access to Composer packages.
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-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.
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-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.