GitLab Patch Release: 16.11.2, 16.10.5, 16.9.7

Today we are releasing versions 16.11.2, 16.10.5, 16.9.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).

These versions contain important bug and 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 fixes for vulnerabilities in dedicated patch releases. There are two types of patch releases: scheduled releases, and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, you can visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here.

For security fixes, 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 patch 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.

Security fixes

Table of security fixes

Title	Severity
ReDoS in branch search when using wildcards	High
ReDoS in markdown render pipeline	Medium
Redos on Discord integrations	Medium
Redos on Google Chat Integration	Medium
Denial of Service Attack via Pin Menu	Medium
DoS by filtering tags and branches via the API	Medium
MR approval via CSRF in SAML SSO	Medium
Banned user from groups can read issues updates via the api	Medium
Require confirmation before linking JWT identity	Medium
View confidential issues title and description of any public project via export	Medium
SSRF via Github importer	Low

ReDoS in branch search when using wildcards

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.7 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. It was possible for an attacker to cause a denial of service by crafting unusual search terms for branch names. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5). It is now mitigated in the latest release and is assigned CVE-2024-2878.

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

ReDoS in markdown render pipeline

An issue has been discovered in GitLab CE/EE affecting all versions before 16.9.7, all versions starting from 16.10 before 16.10.5, all versions starting from 16.11 before 16.11.2. It was possible for an attacker to cause a denial of service using maliciously crafted markdown content. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-2651.

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

Redos on Discord integrations

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.9 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. A problem with the processing logic for Discord Integrations Chat Messages can lead to a regular expression DoS attack on the server. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2023-6682.

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

Redos on Google Chat Integration

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.11 prior to 16.11.2. A problem with the processing logic for Google Chat Messages integration may lead to a regular expression DoS attack on the server. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2023-6688.

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

Denial of Service Attack via Pin Menu

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.11 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. The pins endpoint is susceptible to DoS through a crafted request. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-2454.

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

DoS by filtering tags and branches via the API

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.4 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 where abusing the API to filter branch and tags could lead to Denial of Service. 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-4539.

This vulnerability was reported internally by a GitLab team member Vasilii Iakliushin.

MR approval via CSRF in SAML SSO

An issue has been discovered in GitLab EE affecting all versions from 16.7 before 16.9.7, all versions starting from 16.10 before 16.10.5, all versions starting from 16.11 before 16.11.2. An attacker could force a user with an active SAML session to approve an MR via CSRF. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N, 5.7). It is now mitigated in the latest release and is assigned CVE-2024-4597.

This vulnerability was reported internally by a GitLab team member joernchen.

Banned user from groups can read issues updates via the api

An issue has been discovered in GitLab EE affecting all versions starting from 15.2 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. It was possible to disclose updates to issues to a banned group member using the API. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). It is now mitigated in the latest release and is assigned CVE-2024-1539.

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

Require confirmation before linking JWT identity

An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 in which cross-site request forgery may have been possible on GitLab instances configured to use JWT as an OmniAuth provider. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N, 6.4). It is now mitigated in the latest release and is assigned CVE-2024-1211.

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

View confidential issues title and description of any public project via export

An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. It was possible to disclose via the UI the confidential issues title and description from a public project to unauthorised instance users. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-3976.

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

SSRF via Github importer

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.5 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. GitLab was vulnerable to Server Side Request Forgery when an attacker uses a malicious URL in the markdown image value when importing a GitHub repository. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N, 2.6). It is now mitigated in the latest release and is assigned CVE-2023-6195.

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

Bug fixes

16.11.2

• ci: Remove license scanning job (16.11)
• Backport 'Zoekt: Fix exact search mode' into 16.11
• Return or display Gitlab version if GITLAB_KAS_VERSION is a SHA
• Allow self-managed instances to require licensed seats for Duo Chat
• Merge branch 'release-environment-notification' into '16-11-stable-ee'
• Changed the email validation for only encoded chars
• Backport 'hide archived filter in search when project selected' 16.11
• Cherry-pick MR 151750 into '16-11-stable-ee'
• Fix reconfigure failure if Redis node has Rails Sentinel config

16.10.5

• ci: Remove license scanning job (16.10)
• Upgrade gRPC to v1.62.1
• Return or display Gitlab version if GITLAB_KAS_VERSION is a SHA
• Merge branch 'release-environment-notification' into '16-10-stable-ee'
• Changed the email validation for only encoded chars
• Cherry-pick MR 151750 into '16-10-stable-ee'

16.9.7

• ci: Remove license scanning job (16.9)
• Return or display Gitlab version if GITLAB_KAS_VERSION is a SHA
• Merge branch 'release-environment-notification' into 'master'
• Changed the email validation for only encoded chars
• Cherry-pick MR 151750 into '16-9-stable-ee'

Updating

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

Receive Patch Notifications

To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch 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.