CVE-2023-5332: Patch in third party library Consul requires 'enable-script-checks' to be set to False

This month

MEDIUM 5.9UPGRADEUPGRADE

CVE-2023-5332 is a medium-severity flaw (CVSS 5.9) affecting gitlab, consul. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Published	2023-12-04
Last modified	2026-06-17

Publisher (CNA): GitLab Inc. · Vendor: gitlab · hashicorp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-12-04 07:15 UTCPublished CVE record published
2026-06-17 06:48 UTCUpdated Record last modified

gitlab gitlab UPGRADE

Affected: >= 9.5.0 and < 16.2.8 · >= 16.3.0 and < 16.3.5 · 16.4.0

Fixed in: 16.2.8, 16.3.5

Safe to downgrade to: a release before 9.5.0

1. Check installed version

apt-cache policy gitlab || rpm -q gitlab || gitlab --version

2. UPGRADE to 16.2.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitlab

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitlab

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 9.5.0 (Debian / Ubuntu)

apt-cache madison gitlab sudo apt install gitlab=<VERSION_BEFORE_9.5.0> sudo apt-mark hold gitlab

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gitlab sudo dnf downgrade gitlab-<VERSION_BEFORE_9.5.0> sudo dnf versionlock add gitlab

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

hashicorp consul UPGRADE

Affected: < 0.9.4 · >= 1.0.0 and < 1.0.8 · >= 1.2.0 and < 1.2.4 · 1.1.0

Fixed in: 0.9.4, 1.0.8, 1.2.4

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy consul || rpm -q consul || consul --version

2. UPGRADE to 0.9.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade consul

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade consul

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison consul sudo apt install consul=<VERSION_BEFORE_1.0.0> sudo apt-mark hold consul

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list consul sudo dnf downgrade consul-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add consul

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-5332?

gitlab: upgrade to 16.2.8, 16.3.5; consul: upgrade to 0.9.4, 1.0.8, 1.2.4. Exact commands for each OS are on this page.

Is CVE-2023-5332 being exploited?

CVE-2023-5332 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-5332 affect?

CVE-2023-5332 affects gitlab, consul. Severity is medium (CVSS 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.

How urgent is CVE-2023-5332?

Priority 40/100. Public exploit reference

Software pages

GitLab vulnerabilities · Consul vulnerabilities

Related CVEs

CVE-2026-97229 CRITICAL 10.0 EXPLOITED UPGRADE GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Vulnerability
CVE-2026-93577 CRITICAL 9.9 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.
CVE-2026-89078 CRITICAL 9.9 UPGRADE GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.
CVE-2026-110264 CRITICAL 10.0 UPGRADE An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before 19.0
CVE-2026-16255 MEDIUM 5.9 UPGRADE GitLab has remediated an issue in GitLab EE affecting all versions from 12.0 before 19.3.6, 19.4 before 19.4.3

References

← Back to latest CVEs