CVE-2023-5332

MEDIUMNVD 5.95.9—

5.9

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 v3: 5.9
EG Score: 5.9(medium)
EPSS: 6.0%
KEV: Not listed

Published

December 4, 2023

Last Modified

November 21, 2024

References (4)

cve@gitlabhttps://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8171
cve@gitlabhttps://www.hashicorp.com/blog/protecting-consul-from-rce-risk-in-specific-configurations
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8171
af854a3a-2127-422b-91ae-364da2661108https://www.hashicorp.com/blog/protecting-consul-from-rce-risk-in-specific-configurations

Vendor Advisories for CVE-2023-5332(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

patch-release-gitlab-16-4-1-released
GitLab Security
GitLab Security Release: 16.4.1, 16.3.5, and 16.2.8

Data Freshness Timeline

(refreshed 10× in last 7d / 18× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-24 12:55 UTCEG score recompute
2026-05-24 12:55 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2023-5332?

CVE-2023-5332 is a medium vulnerability published on December 4, 2023. 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.

When was CVE-2023-5332 disclosed?

CVE-2023-5332 was first published in the National Vulnerability Database on December 4, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2023-5332 actively exploited?

CVE-2023-5332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2023-5332?

CVE-2023-5332 has a CVSS v3 base score of 5.9 (NVD).

How do I remediate CVE-2023-5332?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-5332, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-5332

Explore →

Is Your Infrastructure Affected by CVE-2023-5332?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2023-5332

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2023-5332(1)