CVE-2023-3950

Public Exploit
Cleartext Storage of Sensitive Information in GitLab

Description

An information disclosure issue in GitLab EE affecting all versions from 16.2 prior to 16.2.5, and 16.3 prior to 16.3.1 allowed other Group Owners to see the Public Key for a Google Cloud Logging audit event streaming destination, if configured. Owners can now only write the key, not read it.

Remediation

Solution:

  • Upgrade to version 16.2.5 or 16.3.1

Category

5.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.03%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/419675 issue tracking broken link
https://hackerone.com/reports/2079154 broken link exploit permissions required technical description

Frequently Asked Questions

What is the severity of CVE-2023-3950?
CVE-2023-3950 has been scored as a medium severity vulnerability.
How to fix CVE-2023-3950?
To fix CVE-2023-3950: Upgrade to version 16.2.5 or 16.3.1
Is CVE-2023-3950 being actively exploited in the wild?
It is possible that CVE-2023-3950 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-3950?
CVE-2023-3950 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.