First published: Mon Dec 04 2023(Updated: )
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.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab GitLab | >=9.5.0<16.2.8 | |
GitLab GitLab | >=16.3.0<16.3.5 | |
GitLab GitLab | =16.4.0 | |
HashiCorp Consul | <0.9.4 | |
HashiCorp Consul | >=1.0.0<1.0.8 | |
HashiCorp Consul | >=1.2.0<1.2.4 | |
HashiCorp Consul | =1.1.0 |
Upgrade to versions 16.2.8, 16.3.5, 16.4.1 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-5332 is a vulnerability in GitLab that affects versions 9.5.0 to 16.2.8 and versions 16.3.0 to 16.3.5 of GitLab-EE.
CVE-2023-5332 has a severity rating of 8.1 (high).
CVE-2023-5332 affects GitLab-EE versions 9.5.0 to 16.2.8 and versions 16.3.0 to 16.3.5. It requires the 'enable-script-checks' setting in the third-party library Consul to be set to False.
CVE-2023-5332 affects Consul versions up to 0.9.4 and versions 1.0.0 to 1.0.8, and versions 1.2.0 to 1.2.4.
To mitigate the CVE-2023-5332 vulnerability, set the 'enable-script-checks' setting in Consul to False. Refer to the vendor's patch for more details.