Security readout for executives and security teams
Plain-English summary
CVE-2023-5612 let someone read GitLab user email addresses through a tags feed even when users had disabled email visibility in their profile. The business impact is privacy exposure, not system takeover. Affected GitLab versions are before 16.6.6, 16.7.4, and 16.8.1.
Executive priority
Treat this as a moderate-priority privacy exposure. It should be patched promptly, especially on public or partner-facing GitLab instances, but the provided evidence does not indicate ransomware-style urgency or active exploitation.
Technical view
This is a missing authorization issue in GitLab, tracked as CWE-862. The CVSS 3.1 score is 5.3 with network access, low complexity, no privileges, and confidentiality-only impact. The exposed data is user email addresses via tags feed despite profile privacy settings.
Likely exposure
Self-managed GitLab instances running versions before 16.6.6, 16.7.4, or 16.8.1 are the likely exposure group. GitLab.com exposure is not established by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates the issue is remotely reachable without authentication, but the provided public details are limited.
Researcher notes
Public evidence identifies the affected versions, fixed versions, CWE, and exposed data type. The GitLab issue and HackerOne report are listed as permission-restricted, so deeper root-cause and reproduction detail should not be assumed from this bundle.
Mitigation direction
- Upgrade GitLab to 16.8.1, 16.7.4, 16.6.6, or a later supported version.
- Review GitLab’s January 25, 2024 security release guidance for deployment details.
- Prioritize internet-facing GitLab instances and environments with strict user privacy requirements.
- If upgrade timing is constrained, check GitLab vendor guidance for supported temporary mitigations.
Validation and detection
- Inventory all GitLab instances and record their exact version numbers.
- Confirm each instance is at least 16.6.6, 16.7.4, or 16.8.1.
- Review whether user email visibility settings are relied on for privacy controls.
- Check retained access logs for unusual tags feed access, if available.
Public sources used
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-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.
Open ATT&CK lookupCVE-2023-5612 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://about.gitlab.com/releases/2024/01/25/critical-security-release-gitlab-16-8-1-released/CVE reference
- GitLab Issue #428441CVE reference · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2208790CVE 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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.