GitLab Security Release: 16.9.2, 16.8.4, 16.7.7

GitLab Security Advisory

Today we are releasing versions 16.9.2, 16.8.4, 16.7.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.

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

TitleSeverity
Bypassing CODEOWNERS approval allowing to steal protected variablesHigh
Guest with manage group access tokens can rotate and see group access token with owner permissionsMedium

Bypassing CODEOWNERS approval allowing to steal protected variables

An authorization bypass vulnerability was discovered in GitLab affecting versions 11.3 prior to 16.7.7, 16.7.6 prior to 16.8.4, and 16.8.3 prior to 16.9.2. An attacker could bypass CODEOWNERS by utilizing a crafted payload in an old feature branch to perform malicious actions.
This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N, 7.7).
It is now mitigated in the latest release and is assigned CVE-2024-0199.

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

Guest with manage group access tokens can rotate and see group access token with owner permissions

A privilege escalation vulnerability was discovered in GitLab affecting versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2. It was possible for a user with custom role of manage_group_access_tokens to rotate group access tokens with owner privileges.
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-1299.

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

Upgrade Kubectl to the latest stable version

kubectl has been updated to version 1.29.2.

Mattermost Security Updates February 14, 2024

Mattermost has been updated to version 9.5, which contains several patches and security fixes.

Non Security Patches

16.9.2

16.8.4

16.7.7

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.

READ MORE