GitLab Critical Patch Release: 17.1.2, 17.0.4, 16.11.6

GitLab Security Advisory

Today we are releasing versions 17.1.2, 17.0.4, 16.11.6 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 and GitLab Dedicated are 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.

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

TitleSeverity
An attacker can run pipeline jobs as an arbitrary userCritical
Developer user with admin_compliance_framework permission can change group URLMedium
Admin push rules custom role allows creation of project level deploy tokenLow
Package registry vulnerable to manifest confusionLow
User with admin_group_member permission can ban group membersLow
Subdomain takeover in GitLab pagesLow

An attacker can run pipeline jobs as an arbitrary user

An issue was discovered in GitLab CE/EE affecting versions 15.8 prior to 16.11.6, 17.0 prior to 17.0.4, and 17.1 prior to 17.1.2, which allows an attacker to trigger a pipeline as another user under certain circumstances.
This is a critical severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, 9.6).
It is now resolved in the latest release and is assigned CVE-2024-6385.

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

Developer user with admin_compliance_framework permission can change group URL

An issue was discovered in GitLab CE/EE affecting all versions starting from 17.0 prior to 17.0.4 and from 17.1 prior to 17.1.2 where a Developer user with admin_compliance_framework custom role may have been able to modify the URL for a group namespace.
This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N, 4.9).
It is now mitigated in the latest release and is assigned CVE-2024-5257.

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

Admin push rules custom role allows creation of project level deploy token

An issue was discovered in GitLab CE/EE affecting all versions starting from 17.0 prior to 17.0.4 and from 17.1 prior to 17.1.2 where a Guest user with admin_push_rules permission may have been able to create project-level deploy tokens.
This is a low severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N, 3.8).
It is now mitigated in the latest release and is assigned CVE-2024-5470.

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

Package registry vulnerable to manifest confusion

An issue was discovered in GitLab CE/EE affecting all versions starting from 11.8 prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2 where it was possible to upload an NPM package with conflicting package data.
This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N, 3.0).
It is now mitigated in the latest release and is assigned CVE-2024-6595.

This vulnerability was found internally by a GitLab team member Ameya Darshan. Thanks to Darcy Clarke for their work on manifest confusion.

User with admin_group_member permission can ban group members

An issue was discovered in GitLab CE/EE affecting all versions starting from 16.5 prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2 in which a user with admin_group_member custom role permission could ban group members.
This is a low severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N, 2.7).
It is now mitigated in the latest release and is assigned CVE-2024-2880.

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

Subdomain takeover in GitLab Pages

An issue was discovered in GitLab CE/EE affecting all versions prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2, which allows a subdomain takeover in GitLab Pages by checking if the domain is enabled every time the custom domain is resolved.
This is a low severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N, 3.5).
It is now mitigated in the latest release and is assigned CVE-2024-5528.

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

Bug fixes

17.1.2

17.0.4

16.11.6

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.

READ MORE

Leave a Reply

Your email address will not be published. Required fields are marked *