GitLab Security Release: 16.6.1, 16.5.3, 16.4.3

criticalCVE-2023-3401 CVE-2023-6033 CVE-2023-6396 CVE-2023-3949 CVE-2023-5226 CVE-2023-5995

On November 30, 2023, we released versions 16.6.1, 16.5.3, 16.4.3 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 3rd Thursday 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 . 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 XSS and ReDoS in Markdown via Banzai pipeline of Jira High Members with admin_group_member custom permission can add members with higher role High Release Description visible in public projects despite release set as project members only through atom response Medium Manipulate the repository content in the UI (CVE-2023-3401 bypass) Medium External

CSIRTS triage

vendor: GitLab product: GitLabOtheraffected: 16.6.1, 16.5.3, 16.4.3

What: The release contains important security fixes.
Who is affected: All GitLab installations using versions prior to 16.6.1, 16.5.3, or 16.4.3.
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-11-30
Exploitation: Not in CISA KEV at last sync

Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-16-6-1-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-34010.50% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 39% of all scored CVEs.
Low exploitation riskCVE-2023-60330.56% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 43% of all scored CVEs.
Low exploitation riskCVE-2023-39490.54% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 42% of all scored CVEs.
Low exploitation riskCVE-2023-52260.55% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 42% of all scored CVEs.
Low exploitation riskCVE-2023-59950.56% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 42% of all scored CVEs.
Low exploitation riskCVE-2023-49120.58% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 44% of all scored CVEs.
Low exploitation riskCVE-2023-43170.43% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 34% of all scored CVEs.
Low exploitation riskCVE-2023-39640.46% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 37% of all scored CVEs.
Low exploitation riskCVE-2023-46580.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 31% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2023-3401	coverage & exploitation status	NVD · CVE.org
CVE-2023-6033	coverage & exploitation status	NVD · CVE.org
CVE-2023-6396	coverage & exploitation status	NVD · CVE.org
CVE-2023-3949	coverage & exploitation status	NVD · CVE.org
CVE-2023-5226	coverage & exploitation status	NVD · CVE.org
CVE-2023-5995	coverage & exploitation status	NVD · CVE.org
CVE-2023-4912	coverage & exploitation status	NVD · CVE.org
CVE-2023-4317	coverage & exploitation status	NVD · CVE.org
CVE-2023-3964	coverage & exploitation status	NVD · CVE.org
CVE-2023-4658	coverage & exploitation status	NVD · CVE.org
CVE-2023-3443	coverage & exploitation status	NVD · CVE.org
CVE-2023-39417	coverage & exploitation status	NVD · CVE.org
CVE-2022-41409	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

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

medium[UPDATE] [medium] PostgreSQL: Multiple vulnerabilitiescert-bund
unknownDSA-6385-1 pgextwlist - security updatedebian
criticalGitLab Security Release: 16.4.1, 16.3.5, and 16.2.8gitlab
criticalGitLab Security Release: 16.2.2, 16.1.3, and 16.0.8gitlab