CVE-2023-3950: Cleartext Storage of Sensitive Information in GitLab
First published: Fri Sep 01 2023(Updated: )
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.
Credit: cve@gitlab.com cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab GitLab | >=16.2<16.2.5 | |
| GitLab GitLab | >=16.2<16.2.5 | |
| GitLab GitLab | =16.3.0 | |
| GitLab GitLab | =16.3.0 |
Remedy
Upgrade to version 16.2.5 or 16.3.1
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2023-3950?
CVE-2023-3950 is 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.
How does CVE-2023-3950 affect GitLab EE?
CVE-2023-3950 allows other Group Owners to see the Public Key for a Google Cloud Logging audit event streaming destination, if configured.
Which versions of GitLab EE are affected by CVE-2023-3950?
All versions from 16.2 prior to 16.2.5 and 16.3 prior to 16.3.1 are affected by CVE-2023-3950.
What is the severity of CVE-2023-3950?
CVE-2023-3950 has a severity level of medium (3.8).
How can I fix CVE-2023-3950 in GitLab EE?
Owners can now only write the key, not read it, to fix CVE-2023-3950.
- agent/references
- agent/type
- agent/author
- collector/nvd-api
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/weakness
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/last-modified-date
- agent/remedy
- agent/severity
- agent/tags
- agent/first-publish-date
- agent/event
- vendor/gitlab
- canonical/gitlab gitlab
- version/gitlab gitlab/16.2
- version/gitlab gitlab/16.3.0