2024/10/09 アナウンスされたセキュリティリリース情報。クリティカルバグが発見されているためできるだけ早くパッチ適用されることが推奨されています。
以下 GitLab Critical Patch Release: 17.4.2, 17.3.5, 17.2.9 冒頭部分翻訳および原文を掲載します。
///////////////////////////////////////////////////////////////
（翻訳）
GitLab Community Edition (CE) および Enterprise Edition (EE) の GitLab クリティカル パッチ リリース: 17.4.2、17.3.5、17.2.9 の詳細をご覧ください。
本日、GitLab Community Edition (CE) および Enterprise Edition (EE) のバージョン 17.4.2、17.3.5、17.2.9 をリリースします。
これらのバージョンには重要なバグとセキュリティの修正が含まれており、すべてのセルフマネージド GitLab インストールをこれらのバージョンのいずれかにすぐにアップグレードすることを強くお勧めします。GitLab.com ではすでにパッチ適用バージョンが実行されています。GitLab Dedicated のお客様は、何もする必要はありません。
GitLab は、脆弱性の修正をパッチリリースでリリースします。パッチリリースには、スケジュールされたリリースと、重大度の高い脆弱性に対するアドホックの重要なパッチの 2 種類があります。スケジュールされたリリースは、毎月第 2 水曜日と第 4 水曜日に 2 回リリースされます。詳細については、リリース ハンドブックとセキュリティ FAQ をご覧ください。GitLab リリースのブログ投稿はすべて、こちらでご覧いただけます。
セキュリティ修正については、各脆弱性の詳細を記載した問題は、 修正されたリリースの 30 日後に弊社の問題追跡システムで公開されます。
当社は、顧客に公開される GitLab のすべての側面、または顧客データをホストする GitLab のすべての側面が最高のセキュリティ基準を満たすように努めています。セキュリティ衛生を維持する一環として、すべてのお客様に、サポートされているバージョンの最新のパッチ リリースにアップグレードすることを強くお勧めします。GitLab インスタンスを保護するためのベスト プラクティスの詳細については、当社のブログ投稿をご覧ください。
推奨されるアクション
以下に説明する問題の影響を受けるバージョンを実行しているすべてのインストールを、できるだけ早く最新バージョンにアップグレードすることを強くお勧めします。
製品の特定のデプロイメント タイプ (オムニバス、ソース コード、Helm チャートなど) が指定されていない場合は、すべてのタイプが影響を受けることを意味します。
修正パッチリスト、詳細、対応などについては以下原文、もしくは引用元をご参照ください。
GitLab クリティカル パッチ リリース: 17.4.2、17.3.5、17.2.9
https://about.gitlab.com/releases/2024/10/09/patch-release-gitlab-17-4-2-released/
—————————————————————-
（原文）
Learn more about GitLab Critical Patch Release: 17.4.2, 17.3.5, 17.2.9 for GitLab Community Edition (CE) and Enterprise Edition (EE).
Today we are releasing versions 17.4.2, 17.3.5, 17.2.9 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action.
GitLab releases fixes for vulnerabilities in 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 committed 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.
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.
Security fixes
Table of security fixes
Run pipelines on arbitrary branches
An issue was discovered in GitLab EE affecting all versions starting from 12.5 prior to 17.2.9, starting from 17.3, prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows running pipelines on arbitrary branches. 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-2024-9164.
Thanks pwnie for reporting this vulnerability through our HackerOne bug bounty program.
An attacker can impersonate arbitrary user
An issue was discovered in GitLab CE/EE affecting all versions starting from 11.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows an attacker to trigger a pipeline as another user under certain circumstances. This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N, 8.2). It is now mitigated in the latest release and is assigned CVE-2024-8970.
Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program.
SSRF in Analytics Dashboard
An issue has been discovered in GitLab EE affecting all versions starting from 15.10 prior to 17.2.9, from 17.3 prior to 17.3.5, and from 17.4 prior to 17.4.2. Instances with Product Analytics Dashboard configured and enabled could be vulnerable to SSRF attacks. This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N, 8.2). It is now mitigated in the latest release and is assigned CVE-2024-8977.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Viewing diffs of MR with conflicts can be slow
An issue was discovered in GitLab CE/EE affecting all versions starting from 13.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, were viewing diffs of MR with conflicts can be slow. This is a high severity issue (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5). It is now mitigated in the latest release and is assigned CVE-2024-9631.
Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program.
HTMLi in OAuth page
A cross-site scripting issue has been discovered in GitLab affecting all versions starting from 17.1 prior 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2. When authorising a new application, it can be made to render as HTML under specific circumstances. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N, 7.3). It is now mitigated in the latest release and is assigned CVE-2024-6530.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Deploy Keys can push changes to an archived repository
An issue was discovered in GitLab CE/EE affecting all versions starting from 8.16 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows deploy keys to push to an archived repository. 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-9623.
Thanks stevenorman for reporting this vulnerability.
Guests can disclose project templates
An issue has been discovered discovered in GitLab EE/CE affecting all versions starting from 11.4 before 17.2.9, all versions starting from 17.3 before 17.3.5, all versions starting from 17.4 before 17.4.2 It was possible for guest users to disclose project templates using the API. 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-2024-5005.
Thanks js_noob for reporting this vulnerability through our HackerOne bug bounty program.
GitLab instance version disclosed to unauthorized users
An issue has been discovered in GitLab EE affecting all versions starting from 16.6 prior to 17.2.9, from 17.3 prior to 17.3.5, and from 17.4 prior to 17.4.2. It was possible for an unauthenticated attacker to determine the GitLab version number for a GitLab instance. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, 3.7). It is now mitigated in the latest release and is assigned CVE-2024-9596.
This issue was discovered internally by GitLab team member Paul Gascou-Vaillancourt.
Bug fixes
17.4.2
- Backport: fix: Specify an absolute directory for SCHEMA_VERSIONS_DIR to 17-4-stable
- Backport grpc-go v1.67.1 upgrade to 17.4
- Update expected vulnerability in enable_advanced_sast_spec.rb
- Skip multi-version upgrade job for stable branch MRs
- Backport 17.4 Fix label filter by name for search
- Restrict duo pro assignment email to duo pro for sm
- Drop project_id not null constraint ci_deleted_objects
- [Backport] Go-get: fix 401 error for unauthenticated requests
17.3.5
- Backport: fix: Specify an absolute directory for SCHEMA_VERSIONS_DIR to 17-3-stable
- Backport: fix: Allow non-root user to run the bundle-certificates script 17.3
- Skip multi-version upgrade job for stable branch MRs
- Ensure restricted visibility levels is an array – 17.3 backport
17.2.9
- Skip multi-version upgrade job for stable branch MRs
- Ensure restricted visibility levels is an array – 17.2 backport
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.
///////////////////////////////////////////////////////////////
弊社パートナー様はNetworld Dev Portal アカウント（無料）登録いただくと、GitLabパートナー制度や DevSecOps関連提案資料などのパートナー限定コンテンツがご覧いただけます。
DevSecOps全般、GitLab製品または本サイトについては以下よりお問い合わせ下さい。
