GitLab Critical Security Release: 16.3.4 and 16.2.7

criticalCVE-2023-3932 CVE-2023-5009

On September 18, 2023, we released versions 16.3.4 and 16.2.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases: a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. For more information, you can visit our security FAQ . You can see all of our regular and security release blog posts here . In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest security release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Recommended Action We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible . For versions starting from 13.12 before 16.2.7, all versions starting from 16.3 before 16.3.4, see the mitigations offered below. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected. Table of Fixes Title Severity Attacker can abuse scan execution policies to run pipeline as another user high Attacker can abuse scan execution policies to run pipelines as another user An issue has been discovered in GitLab EE affecting all versions starting f

CSIRTS triage

vendor: GitLab product: GitLabOtheraffected: 16.3.4, 16.2.7

What: The release contains important security fixes.
Who is affected: All GitLab installations using versions prior to 16.3.4 or 16.2.7.
Urgency: Remediation is urgent due to the critical severity of the vulnerabilities.
Action: Upgrade to one of the patched versions immediately.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch GitLab

Get an email when a new GitLab advisory drops — max one per day, one-click unsubscribe.

Details

Source: GitLab Security Releases (INTL · vendor-psirt · site)
Severity: critical
Published: 2023-09-18
Exploitation: Not in CISA KEV at last sync

Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-16-3-4-released/

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2023-39320.88% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 55% of all scored CVEs.
Moderate exploitation riskCVE-2023-50098.3% 30-day exploitation probability. Patch within normal cadence, watch for KEV listing. Riskier than 94% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2023-3932	coverage & exploitation status	NVD · CVE.org
CVE-2023-5009	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

criticalGitLab Security Release: 16.2.2, 16.1.3, and 16.0.8gitlab