GitLab Patch Release: 17.0.2, 16.11.4, 16.10.7

Today we are releasing versions 17.0.2, 16.11.4, 16.10.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 gomod dependency linker	Medium
ReDoS in CI interpolation (fix bypass)	Medium
ReDoS in Asana integration issue mapping when webhook is called	Medium
XSS and content injection when viewing raw XHTML files on IOS devices	Medium
Missing agentk request validation could cause KAS to panic	Low

ReDoS in gomod dependency linker

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.1 prior to 16.10.7, starting from 16.11 prior to 16.11.4, and starting from 17.0 prior to 17.0.2. It was possible for an attacker to cause a denial of service using maliciously crafted file. 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-1495.

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

ReDoS in CI interpolation (fix bypass)

An issue has been discovered in GitLab CE/EE affecting all versions prior to 16.10.7, starting from 16.11 prior to 16.11.4, and starting from 17.0 prior to 17.0.2. A vulnerability in GitLab's CI/CD pipeline editor could allow for denial of service attacks through maliciously crafted configuration files. 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-1736.

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

ReDoS in Asana integration issue mapping when webhook is called

An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.4 prior to 16.10.7, starting from 16.11 prior to 16.11.4, and starting from 17.0 prior to 17.0.2. A vulnerability in GitLab's Asana integration allowed an attacker to potentially cause a regular expression denial of service by sending specially crafted requests. 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-1963.

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

XSS and content injection when viewing raw XHTML files on iOS devices

A cross-site scripting issue has been discovered in GitLab affecting all versions starting from 5.1 before 16.10.7, all versions starting from 16.11 before 16.11.4, all versions starting from 17.0 before 17.0.2. When viewing an XML file in a repository in raw mode, it can be made to render as HTML if viewed under specific circumstances. This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N, 4.4). It is now mitigated in the latest release and is assigned CVE-2024-4201.

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

Missing agentk request validation could cause KAS to panic

DoS in KAS in GitLab CE/EE affecting all versions from 16.10.0 prior to 16.10.6 and 16.11.0 prior to 16.11.3 allows an attacker to crash KAS via crafted gRPC requests. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L, 3.1). It is now mitigated in the latest release and is assigned CVE-2024-5469.

This vulnerability has been discovered internally by the Environments team.

Bug fixes

17.0.2

• Makefile: update Git versions (v17.0 backport)
• Update VERSION files
• Docs: Backport Dedicated AI updates
• Fix failing specs in 17-0-stable-ee
• Include headers in LfsDownloadObject
• [17.0] Deprecate support for Ubuntu 18.04

16.11.4

• Makefile: update Git versions (v16.11 backport)
• Backport 'run-release-environment-for-tag-commits' into 16.11
• Dedicated AI updates
• Speed up as-if-foss Rubocop
• Inclusion of headers in LfsDownloadObject for GitHub imports
• Fix failing specs on 16-11-stable
• Stop orphaning pages deployments on Geo secondaries on 16.11

16.10.7

• Makefile: update Git versions (v16.10 backport)
• Backport 'run-release-environment-for-tag-commits' into 16.10
• Fix failing specs on 16-10-stable-ee
• Stop orphaning pages deployments on Geo secondaries on 16.10

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.