Vulnerability record · CVE-2023-5332 · published 4 December 2023
CVE-2023-5332: Gitlab vulnerability
Gitlab · Gitlab
Patch in third party library Consul requires 'enable-script-checks' to be set to False. This was required to enable a patch by the vendor. Without this setting the patch could be bypassed. This only affects GitLab-EE.
Description
Patch in third party library Consul requires 'enable-script-checks' to be set to False. This was required to enable a patch by the vendor. Without this setting the patch could be bypassed. This only affects GitLab-EE.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8171 | ExploitIssue Tracking |
| https://www.hashicorp.com/blog/protecting-consul-from-rce-risk-in-specific-configurations | PatchVendor Advisory |
| https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8171 | ExploitIssue Tracking |
| https://www.hashicorp.com/blog/protecting-consul-from-rce-risk-in-specific-configurations | PatchVendor Advisory |
Track CVE-2023-5332 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2023-5332), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.