Security readout for executives and security teams
Plain-English summary
This GitLab issue could expose the email address of someone who created a Service Desk issue. The documented impact is limited confidentiality loss, not system takeover or data modification. It matters most where Service Desk is used for sensitive or anonymous reporting.
Executive priority
Handle through normal patch governance unless Service Desk supports sensitive, anonymous, or regulated reporting. Escalate locally if exposed email addresses could create privacy, retaliation, or compliance concerns.
Technical view
CVE-2023-1936 affects GitLab CE/EE 13.7 before 15.11.10, 16.0 before 16.0.6, and 16.1 before 16.1.1. The flaw is CWE-359 exposure of private personal information. CVSS 3.1 is 3.5 with network access, low complexity, low privileges, required user interaction, and confidentiality-only impact.
Likely exposure
Exposure is likely limited to affected GitLab CE/EE instances using Service Desk issue workflows where creator email addresses should remain private.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. A HackerOne report is referenced, but this analysis cannot infer real-world exploitation beyond the provided sources.
Researcher notes
The CVSS vector indicates no integrity or availability impact. Required user interaction and low privileges reduce urgency, but the affected data is personal information. Evidence is incomplete on practical exploit prevalence and exact remediation notes beyond fixed version boundaries.
Mitigation direction
- Upgrade affected GitLab CE/EE instances to fixed or later supported versions.
- Prioritize 15.11.10, 16.0.6, 16.1.1, or later according to your release line.
- Check GitLab guidance before relying on any configuration workaround.
- Review Service Desk privacy expectations and communicate potential email exposure where appropriate.
Validation and detection
- Inventory GitLab CE/EE versions across self-managed environments.
- Confirm instances are not running affected version ranges.
- Determine whether Service Desk issue creation was enabled during the vulnerable window.
- Review affected projects where reporter email confidentiality is operationally important.
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-359: 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-1936 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
- 3.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:L/UI:R/S:U/C:L/I:N/A:N2.11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.5LowVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #405150CVE reference · issue-tracking
- HackerOne Bug Bounty Report #1933829CVE 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.
Exposure of Private Personal Information to an Unauthorized Actor
Exposure of Private Personal Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.