GitLab Security Release: 16.8.2, 16.7.5, 16.6.7

Today we are releasing versions 16.8.2, 16.7.5, 16.6.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 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
Restrict group access token creation for custom roles	Medium
Project maintainers can bypass group's scan result policy block_branch_modification setting	Medium
ReDoS in CI/CD Pipeline Editor while verifying Pipeline syntax	Medium
Resource exhaustion using GraphQL vulnerabilitiesCountByDay	Medium

Restrict group access token creation for custom roles

An issue has been discovered in GitLab EE affecting all versions starting from 16.8 before 16.8.2. When a user is assigned a custom role with manage_group_access_tokens permission, they may be able to create group access tokens with Owner privileges, which may lead to privilege escalation. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-1250.

This vulnerability has been discovered internally by GitLab team member Rohit Shambhuni.

Project maintainers can bypass group's scan result policy block_branch_modification setting

An issue has been discovered in GitLab EE affecting all versions from 16.4 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows a maintainer to change the name of a protected branch that bypasses the security policy added to block MR. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H, 6.7). It is now mitigated in the latest release and is assigned CVE-2023-6840.

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

ReDoS in CI/CD Pipeline Editor while verifying Pipeline syntax.

A denial of service vulnerability was identified in GitLab CE/EE, affecting all versions from 15.11 prior to 16.6.7, 16.7 prior to 16.7.5 and 16.8 prior to 16.8.2 which allows an attacker to spike the GitLab instance resource usage resulting in service degradation. 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-6386.

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

Resource exhaustion using GraphQL vulnerabilitiesCountByDay

An issue has been discovered in GitLab EE affecting all versions from 13.3.0 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows an attacker to do a resource exhaustion using GraphQL vulnerabilitiesCountByDay. 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-1066.

This vulnerability has been discovered internally by GitLab team member Brian Williams.

Update to PostgreSQL 14.10 and 13.13

PostgreSQL has been updated.

Non Security Patches

16.8.2

• Gitaly: properly set PYTHON_TAG in CI, for Dockerfile (16.8)
• Update GDK base build image and update QA GEM
• Revert "Validate scopes for importing collaborators"
• Backport !142896 into 16.8 stable branch
• Update dependency prometheus-client-mmap to '~> 1.1', '>= 1.1.1'
• Defer ConnectionPool instrumentation setup
• Add item_to_preload method in helper and migrations to prevent N+1 query
• Fix bug for devfile with multiple container components
• Backport "Fix Redis 6.0 compatibility breakage with Sidekiq 7 gem"
• Finalize UUID backfilling before performing cleanup
• Backport - Ensure post upgrade steps are run after geo_pg_upgrade

16.7.5

• Update dependency prometheus-client-mmap to '~> 1.1', '>= 1.1.1'
• Backport UUID migration finalization to 16.7

16.6.7

• Add missing IMAGE_TAG_EXT to referenced PostgreSQL image
• Backport: Update GDK base build image
• [Backport] Control runner tags for package promotion via env vars

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.