Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2022.3703
GitLab Security Release: 15.2.1, 15.1.4, and 15.0.5
29 July 2022
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: GitLab Community Edition (CE)
Enterprise Edition (EE)
Publisher: GitLab
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Resolution: Patch/Upgrade
CVE Names: CVE-2022-2539 CVE-2022-2534 CVE-2022-2531
CVE-2022-2512 CVE-2022-2501 CVE-2022-2500
CVE-2022-2499 CVE-2022-2498 CVE-2022-2497
CVE-2022-2459 CVE-2022-2456 CVE-2022-2417
CVE-2022-2326 CVE-2022-2307 CVE-2022-2303
CVE-2022-2095
Original Bulletin:
https://about.gitlab.com/releases/2022/07/28/security-release-gitlab-15-2-1-released
Comment: CVSS (Max): 6.5 CVE-2022-2512 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
CVSS Source: GitLab
Calculator: https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- --------------------------BEGIN INCLUDED TEXT--------------------
GitLab Security Release: 15.2.1, 15.1.4, and 15.0.5
Today we are releasing versions 15.2.1, 15.1.4, and 15.0.5 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.
When no specific deployment type (omnibus, source code, helm chart, etc.) of a
product is mentioned, this means all types are affected.
Breaking change
In July 2019 we fixed a vulnerability related to very large CI/CD configuration
files and the ci_yaml_limit_size feature flag was introduced as a way to
disable the patch, if needed. We are now removing that feature flag as well, to
remove the possibility of disabling the patch.
You are not affected by this change if the feature flag was not manually
disabled. You can refer to our documentation for instructions on how to check
the state of a feature flag.
If you've disabled this feature flag and like to maintain the existing behavior
and avoid a breaking change, you can refer to our documentation for
instructions on how to configure the size of your CI/CD configuration file from
the rails console.
Table of Fixes
Title Severity
Revoke access to confidential notes todos medium
Pipeline subscriptions trigger new pipelines with the wrong author medium
Ability to gain access to private project through an email invite by medium
using other user's email address as an unverified secondary email
Import via git protocol allows to bypass checks on repository medium
Unauthenticated IP allowlist bypass when accessing job artifacts medium
through GitLab Pages
Maintainer can leak Packagist and other integration access tokens by medium
changing integration URL
Unauthenticated access to victims Grafana datasources through path medium
traversal
Unauthorized users can filter issues by contact and organization medium
Malicious Maintainer may change the visibility of project or a group medium
Stored XSS in job error messages medium
Enforced group MFA can be bypassed when using Resource Owner Password medium
Credentials grant
Non project members can view public project's Deploy Keys medium
IDOR in project with Jira integration leaks project owner's other low
projects Jira issues
Group Bot Users and Tokens not deleted after group deletion low
Email invited members can join projects even after the member lock has low
been enabled
Datadog integration returns user emails low
Revoke access to confidential notes todos
An issue has been discovered in GitLab CE/EE affecting all versions starting
from 15.0 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1. Membership changes are not reflected
in TODO for confidential notes, allowing a former project members to read
updates via TODOs. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/
UI:N/S:U/C:H/I:N/A:N, 6.5). It is now mitigated in the latest release and is
assigned CVE-2022-2512.
This vulnerability has been discovered internally by the GitLab team.
Pipeline subscriptions trigger new pipelines with the wrong author
An issue in pipeline subscriptions in GitLab EE affecting all versions starting
from 12.8 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1 triggered new pipelines with the
person who created the tag as the pipeline creator instead of the
subscription's author. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L
/UI:R/S:U/C:H/I:H/A:N, 6.4). It is now mitigated in the latest release and is
assigned CVE-2022-2498.
Thanks vaib25vicky for reporting this vulnerability through our HackerOne bug
bounty program.
Ability to gain access to private project through an email invite by using
other user's email address as an unverified secondary email
An issue has been discovered in GitLab CE/EE affecting all versions before
15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting
from 15.2 before 15.2.1. It may be possible to gain access to a private project
through an email invite by using other user's email address as an unverified
secondary email. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/
S:U/C:H/I:H/A:N, 6.4). It is now mitigated in the latest release and is
assigned CVE-2022-2326.
Thanks vaib25vicky for reporting this vulnerability through our HackerOne bug
bounty program.
Import via git protocol allows to bypass checks on repository
Insufficient validation in GitLab CE/EE affecting all versions starting from
12.10 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1 allows an authenticated and
authorised user to import a project that includes branch names which are 40
hexadecimal characters, which could be abused in supply chain attacks where a
victim pinned to a specific Git commit of the project. This is a medium
severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N, 6.2). It is now
mitigated in the latest release and is assigned CVE-2022-2417.
This vulnerability has been discovered internally by the GitLab team.
Unauthenticated IP allowlist bypass when accessing job artifacts through GitLab
Pages
An improper access control issue in GitLab EE affecting all versions starting
from 12.0 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1 allows an attacker to bypass IP
allow-listing and download artifacts. This attack only bypasses IP
allow-listing, proper permissions are still required. This is a medium severity
issue (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, 5.9). It is now mitigated
in the latest release and is assigned CVE-2022-2501.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug
bounty program.
Maintainer can leak Packagist and other integration access tokens by changing
integration URL
An issue has been discovered in GitLab CE/EE affecting all versions starting
from 12.6 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1. A malicious maintainer could
exfiltrate an integration's access token by modifying the integration URL such
that authenticated requests are sent to an attacker controlled server. This is
a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N, 5.5). It
is now mitigated in the latest release and is assigned CVE-2022-2497.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug
bounty program.
Unauthenticated access to victims Grafana datasources through path traversal
An issue has been discovered in GitLab EE affecting all versions starting from
12.5 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions
starting from 15.2 before 15.2.1. GitLab was not performing correct
authentication on Grafana API under specific conditions allowing
unauthenticated users to perform queries through a path traversal
vulnerability. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/
S:U/C:L/I:N/A:N, 5.3). It is now mitigated in the latest release and is
assigned CVE-2022-2531.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug
bounty program.
Unauthorized users can filter issues by contact and organization
An issue has been discovered in GitLab CE/EE affecting all versions starting
from 14.6 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1, allowed a project member to filter
issues by contact and organization. This is a medium severity issue (CVSS:3.1/
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3). It is now mitigated in the latest
release and is assigned CVE-2022-2539.
This vulnerability has been discovered internally by the GitLab team.
Malicious Maintainer may change the visibility of project or a group
An issue has been discovered in GitLab CE/EE affecting all versions before
15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting
from 15.2 before 15.2.1. It may be possible for malicious group or project
maintainers to change their corresponding group or project visibility by
crafting a malicious POST request. This is a medium severity issue (CVSS:3.1/
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, 4.9). It is now mitigated in the latest
release and is assigned CVE-2022-2456.
Thanks suruli for reporting this vulnerability through our HackerOne bug bounty
program.
Stored XSS in job error messages
A cross-site scripting issue has been discovered in GitLab CE/EE affecting all
versions before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1. A stored XSS flaw in job error
messages allows attackers to perform arbitrary actions on behalf of victims at
client side. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/
C:L/I:L/A:N, 4.4). It is now mitigated in the latest release and is assigned
CVE-2022-2500.
Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty
program.
Enforced group MFA can be bypassed when using Resource Owner Password
Credentials grant
An issue has been discovered in GitLab CE/EE affecting all versions before
15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting
from 15.2 before 15.2.1. It may be possible for group members to bypass 2FA
enforcement enabled at the group level by using Resource Owner Password
Credentials grant to obtain an access token without using 2FA. This is a medium
severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, 4.3). It is now
mitigated in the latest release and is assigned CVE-2022-2303.
Thanks albatraoz for reporting this vulnerability through our HackerOne bug
bounty program.
Non project members can view public project's Deploy Keys
An improper access control check in GitLab CE/EE affecting all versions
starting from 13.7 before 15.0.5, all versions starting from 15.1 before
15.1.4, all versions starting from 15.2 before 15.2.1 allows a malicious
authenticated user to view a public project's Deploy Key's public fingerprint
and name when that key has write permission. Note that GitLab never asks for
nor stores the private key. This is a medium severity issue (CVSS:3.1/AV:N/AC:L
/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). It is now mitigated in the latest release and
is assigned CVE-2022-2095.
Thanks jimeno for reporting this vulnerability through our HackerOne bug bounty
program.
IDOR in project with Jira integration leaks project owner's other projects Jira
issues
An issue has been discovered in GitLab EE affecting all versions starting from
13.10 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1. GitLab's Jira integration has an
insecure direct object reference vulnerability that may be exploited by an
attacker to leak Jira issues. This is a low severity issue (CVSS:3.1/AV:N/AC:H/
PR:L/UI:N/S:C/C:L/I:N/A:N, 3.5). It is now mitigated in the latest release and
is assigned CVE-2022-2499.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug
bounty program.
Group Bot Users and Tokens not deleted after group deletion
A lack of cascading deletes in GitLab CE/EE affecting all versions starting
from 13.0 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1 allows a malicious Group Owner to
retain a usable Group Access Token even after the Group is deleted, though the
APIs usable by that token are limited. This is a low severity issue (CVSS:3.1/
AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N, 3.5). It is now mitigated in the latest
release and is assigned CVE-2022-2307.
This vulnerability has been discovered by the JiHu team.
Email invited members can join projects even after the member lock has been
enabled
An issue has been discovered in GitLab EE affecting all versions before 15.0.5,
all versions starting from 15.1 before 15.1.4, all versions starting from 15.2
before 15.2.1. It may be possible for email invited members to join a project
even after the Group Owner has enabled the setting to prevent members from
being added to projects in a group, if the invite was sent before the setting
was enabled. 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-2022-2459.
Thanks justas_b for reporting this vulnerability through our HackerOne bug
bounty program.
Datadog integration returns user emails
An issue has been discovered in GitLab CE/EE affecting all versions starting
from 9.3 before 15.0.5, all versions starting from 15.1 before 15.1.4, all
versions starting from 15.2 before 15.2.1. GitLab was returning contributor
emails due to improper data handling in the Datadog integration. This is a low
severity issue (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N, 2.2). It is now
mitigated in the latest release and is assigned CVE-2022-2534.
This vulnerability has been discovered internally by the GitLab team.
Update bzip2
The version of bzip2 has been updated to 1.0.8 in order to mitigate security
concerns.
Versions affected
Affects all versions of GitLab Omnibus.
Update exiftool
The version of exiftool has been updated to 12.42 in order to mitigate security
concerns.
Versions affected
Affects all versions of GitLab Omnibus.
Updating
To update GitLab, see the Update page. To update Gitlab Runner, see the
Updating the Runner page.
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: https://auscert.org.au/gpg-key/
iQIVAwUBYuM4FskNZI30y1K9AQgkhQ/8DruoGALZeIylV82JmtZhQpyRK92zWZeC
J04FJrZg4Aib9X13XmDjJzBTzbLPqQS6WN3aob8qZkuHh24mORlg9mXhAKLYNJDy
vhFDAuZg1tpiBRFhgIayVfAl6oMG4TL8u5FbwgrUtTrzaBL0fZ0mF9HhhYZa4BqL
G6oGjCGAShPcFP6LK3h55LY9mWgpyr6D2ldbQerTAYtc3G3Carf2H2TDPAnK8Vjg
4etrNAcAzsCSvKR2C9/rhUnBE0ORFR29xm/Lqi5xHFeG9GRQyqrdmO0W43HWJkur
/BZfDCLojC0nprp7uESRtfHJnCBgOkqXn2JfCYQ6VFFweuAx/sr29Vioqav9MKvk
2wXP7SmOKDxthlFjkXlooN25nvlUaiFmyim/znbW26XHPdvLuvDMQKAo3XKeaGph
nnpBLE2GyZpcPwrQ6+oCxj0Jy4nDMAcPl9yOwuHxUUkoboIcukTtnbo5KOb3k0ni
/6sfHWug4UKC7wz8X18n0SQlUvLtOCNU8E+Fn3PowwkwFopCzrpOTm6OIRidpi/j
XZ3TYu7xz6NISYG13YyQxfmc0JjI/4D4xfrC9zEFvt+N9jnqhXbsOjugbnSBi3ay
/MT+Be9qdV0b7MA9XAYg2L9CDfG+6GYJzU8O9YBCbHkdxvknHtEH5ZcAfcYTPQgd
eJjRfI8C5rg=
=RB+X
-----END PGP SIGNATURE-----