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

                            CERT-Renater

                 Note d'Information No. 2023/VULN191

_____________________________________________________________________

DATE                : 12/05/2023

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running GitLab versions prior to 15.11.3,
                                      15.10.7, 15.9.8.

=====================================================================
https://about.gitlab.com/releases/2023/05/10/security-release-gitlab-15-11-3-released/
_____________________________________________________________________

  GitLab Coordinated Security Release: 15.11.3, 15.10.7, 15.9.8

Learn more about GitLab Security Release: 15.11.3, 15.10.7, 15.9.8
for GitLab Community Edition (CE) and Enterprise Edition (EE).

Today we are releasing versions 15.11.3, 15.10.7, 15.9.8 for GitLab
Community Edition (CE) and Enterprise Edition (EE). This is a
coordinated security release, aligning with a disclosure date
provided by Git.

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 three types of security releases: a monthly,
scheduled security release, released a week after the feature
release (which deploys on the 22nd of each month), ad-hoc
security releases for critical vulnerabilities, as well as
coordinated 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.

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
Smuggling code changes via merge requests with refs/replace Medium


Smuggling code changes via merge requests with refs/replace

An issue has been discovered in GitLab affecting all versions
before 15.9.8, 15.10.0 before 15.10.7, and 15.11.0 before
15.11.3. A malicious developer could use a git feature
called refs/replace to smuggle content into a merge request
which would not be visible during review in the UI. This is
a medium severity issue
(CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N, 6.3 Medium).
It is now mitigated in the latest release and is assigned
CVE-2023-2181.

Thanks inspector-ambitious for reporting this vulnerability
through our HackerOne bug bounty program.


Non-security patches

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

Into 15.11.3:

     Restrict bigint cleanup migrations to GitLab.com only
     Revert migration squash that breaks 15.11
     [15.11] ci: Fix omnibus trigger target branch for MR
             targeting stable branches
     Fix custom template import permission
     [15.11] Fix for the rebase merge request state being shown
             incorrectly
     Back with UNSTRUCTURED_RAILS_LOG environment variable
     Fix issue description keeping autosave after save

Into 15.10.7:

     [15.10] ci: Fix omnibus trigger target branch for MR
              targeting stable branches
     Fix custom template import permission
     [15.10] Fix for the rebase merge request state being
              shown incorrectly

Into 15.9.8:

     [15.9] ci: Fix omnibus trigger target branch for MR
             targeting stable branches
     [15.9] Fix for the rebase merge request state being shown
             incorrectly

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 +
=========================================================