CVE-2023-3950 Cleartext Storage of Sensitive Information in GitLab
Group owners can view sensitive public keys for Google Cloud Logging audit destinations if configured, exposing sensitive information.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-3950?
CVE-2023-3950 is a medium-severity vulnerability in Gitlab Gitlab, published on 1 Sep 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Official 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.
Weakness: CWE-312
Which versions are affected by CVE-2023-3950?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 16.2.0 | 16.2.5, 16.3.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-3950?
Upgrade gitlab to a fixed version for your release line: 16.2.5 or 16.3.1.
Is CVE-2023-3950 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3950 exists.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2023-3950, GHSA-5xhg-wqm3-8ww2.