patch-release-gitlab-16-7-2-released
GitLab Critical Security Release: 16.7.2, 16.6.4, 16.5.6
🔗 CVE IDs covered (5)
📋 Description
On January 11, 2024, we released versions 16.7.2, 16.6.4, 16.5.6 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 fixes for security vulnerabilities in security releases.
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. If you have not upgraded yet, be aware that there is a newer patch that includes additional fixes for recently discovered DB migration issue. Please upgrade to 16.7.3, 16.6.5, 16.5.7, or newer to prevent the migration issue.
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
Account Takeover via password reset without user interactions
Critical
Bypass CODEOWNERS approval removal
High
Attacker can abuse Slack/Mattermost integrations to execute slash commands as another user
High
Workspaces able to be created under different root namespace
Medium
Commit signature validation ignores headers after signature
Low
Account Takeover via Pass…