=====================================================================

                              CERT-Renater

                    Note d'Information No. 2023/VULN334

_____________________________________________________________________

DATE                : 20/09/2023

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running GitLab versions prior to 16.3.4,
                                            16.2.7.

=====================================================================
https://about.gitlab.com/releases/2023/09/18/security-release-gitlab-16-3-4-released/
_____________________________________________________________________


  GitLab Critical Security Release: 16.3.4 and 16.2.7

Learn more about GitLab Critical Security Release: 16.3.4 and 16.2.7
for GitLab Community Edition (CE) and Enterprise Edition (EE).

Today we are releasing versions 16.3.4 and 16.2.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 22nd 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. For versions prior to 16.2,
see the mitigations offered below.

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
Attacker can abuse scan execution policies to run pipeline
as another user 	critical


Attacker can abuse scan execution policies to run pipelines
as another user

An issue has been discovered in GitLab EE affecting all
versions starting from 13.12 before 16.2.7 and all versions
starting from 16.3 before 16.3.4. It was possible for an
attacker to run pipelines as an arbitrary user via scheduled
security scan policies. This was a bypass of CVE-2023-3932
showing additional impact. 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 mitigated in the latest release and is assigned
CVE-2023-5009.

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


Mitigations for versions prior to 16.2

Instances running versions earlier than 16.2 are vulnerable if
both of the features below are enabled at the same time. In
order to mitigate this vulnerability in situations where it's
not possible to upgrade, it is required to disable one or both
features.

     Direct transfers
     Security policies

If both features are turned on, the instance is in a vulnerable
state.


Non Security Patches

This security release also includes the following non-security
patches.


16.3.4

     Use new indexer, fix removing blobs from index
     Backport "Fix Geo secondary proxying Git pulls unnecessarily"
to 16.3


16.2.7

     Revert "Merge branch 'md-play-all-skipped-button' into 'master'"


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.

=========================================================
+ CERT-RENATER        |    tel : 01-53-94-20-44         +
+ 23/25 Rue Daviel    |    fax : 01-53-94-20-41         +
+ 75013 Paris         |   email:cert@support.renater.fr +
=========================================================