Security readout for executives and security teams
Plain-English summary
CVE-2023-3950 is a GitLab EE information disclosure issue. In specific 16.2 and 16.3 releases, Group Owners could view the Public Key for a Google Cloud Logging audit event streaming destination when configured. GitLab changed behavior so owners can write the key but not read it.
Executive priority
Treat as a targeted medium-risk configuration issue, not an internet-wide emergency. Prioritize affected GitLab EE environments that use Google Cloud Logging audit streaming and have many Group Owners or weak owner-account controls.
Technical view
The issue is CWE-312, cleartext storage of sensitive information. It affects GitLab EE 16.2 before 16.2.5 and 16.3 before 16.3.1. CVSS is 5.5, requiring high privileges, network access, no user interaction, and causing limited confidentiality and integrity impact.
Likely exposure
Exposure is limited to GitLab EE instances on affected versions with Google Cloud Logging audit event streaming configured. The actor must already be a Group Owner, so risk is mainly insider, delegated-admin, or compromised-owner-account exposure.
Exploitation context
The supplied sources do not indicate known active exploitation, and this CVE is not listed as KEV. The HackerOne and GitLab references indicate a permissions-related disclosure path, but detailed public access may be restricted.
Researcher notes
The core exposure requires privileged Group Owner access and a specific audit streaming configuration. Public technical detail appears limited by permissions on referenced issue sources. Avoid assuming broader secret disclosure beyond the stated Google Cloud Logging public key field.
Mitigation direction
- Upgrade GitLab EE 16.2 to 16.2.5 or later.
- Upgrade GitLab EE 16.3 to 16.3.1 or later.
- Review Google Cloud Logging audit event streaming configuration.
- Review Group Owner membership and remove unnecessary owners.
- Check GitLab vendor guidance for any key-handling recommendations.
Validation and detection
- Identify GitLab EE instances running 16.2 or 16.3.
- Confirm whether Google Cloud Logging audit streaming is configured.
- Verify installed version is 16.2.5, 16.3.1, or later.
- Confirm Group Owners cannot read the configured public key.
- Review access logs for unusual Group Owner activity, if available.
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-312: 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-3950 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/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.
SSVC decision data
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:H/UI:N/S:C/C:L/I:L/A:N2.32.7GitLabVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #419675CVE reference, GitLab · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2079154CVE reference, GitLab · 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.
Cleartext Storage of Sensitive Information
Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.