GitLab Security Release: 16.10.1, 16.9.3, 16.8.5

Today we are releasing versions 16.10.1, 16.9.3, 16.8.5 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
Stored-XSS injected in Wiki page via Banzai pipeline	High
DOS using crafted emojis	Medium

Stored-XSS injected in Wiki page via Banzai pipeline

An issue has been discovered in GitLab CE/EE affecting all versions before 16.8.5, all versions starting from 16.9 before 16.9.3, all versions starting from 16.10 before 16.10.1. A wiki page with a crafted payload may lead to a Stored XSS, allowing attackers to perform arbitrary actions on behalf of victims. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7). It is now mitigated in the latest release and is assigned CVE-2023-6371.

Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program.

DOS using crafted emojis

An issue has been discovered in GitLab CE/EE affecting all versions before 16.8.5, all versions starting from 16.9 before 16.9.3, all versions starting from 16.10 before 16.10.1. It was possible for an attacker to cause a denial of service using malicious crafted description parameter for labels. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, 4.3). It is now mitigated in the latest release and is assigned CVE-2024-2818.

Thanks Quintin Crist of Trend Micro for reporting this vulnerability to us.

Bump PostgreSQL to 13.14, 14.11

The PostgreSQL project released an update so we are updating to versions 13.14 and 14.11.

Non Security Patches

16.10.1

• CI: bump CI_TOOLS_VERSIONS to 5.8.0 (Backport 16.10)
• Backport protobuf and pgx upgrades [16.10]
• Fix new project group templates pagination (16-10-stable-ee)
• Update redis-client to v0.21.1

16.9.3

• CI: bump CI_TOOLS_VERSIONS to 5.8.0 (Backport 16.9)
• Backport protobuf and pgx upgrades [16.9]
• Fix detect-tests CI job
• Collect the artifacts from the same namespace
• Fix new project group templates pagination (16-9-stable-ee)
• Backport: RSpec changes for .com handling nightly packages

16.8.5

• CI: bump CI_TOOLS_VERSIONS to 5.8.0 (Backport 16.8)
• Fix detect-tests CI job
• Backport: RSpec changes for .com handling nightly packages
• Backport c2a94ae8 for creating stable tag for 16-8-stable

Updating

To update GitLab, see the Update page. To update Gitlab Runner, see the Updating the Runner page.

Receive Security Release Notifications

To receive security release blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our security release RSS feed or our RSS feed for all releases.

We’re combining patch and security releases

This improvement in our release process matches the industry standard and will help GitLab users get information about security and bug fixes sooner, read the blog post here.