2024/12/11 アナウンスされたセキュリティリリース情報。緊急レベルではないようですが「優先度：高」のセキュリティ修正があり、そのうちの1件は、対象バージョン範囲がひろく『9.4 から 17.4.6 まで、17.5 から 17.5.4 まで、および 17.6 から 17.6.2 までのすべてのバージョン 』(9.4がリリースされたのは 2017/7/22) とアナウンスされています。一度、確認いただくことをが推奨されるレベルと考えられます。
以下 GitLab Patch Release: 17.6.2, 17.5.4, 17.4.6 冒頭部分翻訳および原文を掲載します。
原文へのリンクは上記もしくは以下URLから
https://about.gitlab.com/releases/2024/12/11/patch-release-gitlab-17-6-2-released/?utm_medium=email&utm_source=marketo&utm_campaign=security+release+email&December+10+2024
///////////////////////////////////////////////////////////////
（翻訳）
GitLab Community Edition (CE) および Enterprise Edition (EE) の GitLab パッチ リリース: 17.6.2、17.5.4、17.4.6 の詳細をご覧ください。
本日、GitLab Community Edition (CE) および Enterprise Edition (EE) のバージョン 17.6.2、17.5.4、17.4.6 をリリースします。
これらのバージョンには重要なバグとセキュリティの修正が含まれており、すべてのセルフマネージド GitLab インストールをこれらのバージョンのいずれかにすぐにアップグレードすることを強くお勧めします。GitLab.com ではすでにパッチ適用バージョンが実行されています。GitLab Dedicated のお客様は、何もする必要はありません。
GitLab は、脆弱性の修正をパッチリリースでリリースします。パッチリリースには、スケジュールされたリリースと、重大度の高い脆弱性に対するアドホックの重要なパッチの 2 種類があります。スケジュールされたリリースは、毎月第 2 水曜日と第 4 水曜日に 2 回リリースされます。詳細については、リリース ハンドブックとセキュリティ FAQ をご覧ください。GitLab リリースのブログ投稿はすべて、こちらでご覧いただけます。
セキュリティ修正については、各脆弱性の詳細を記載した問題は、 修正されたリリースの 30 日後に弊社の問題追跡システムで公開されます。
当社は、顧客に公開される GitLab のすべての側面、または顧客データをホストする GitLab のすべての側面が最高のセキュリティ基準を満たすように努めています。セキュリティ衛生を維持する一環として、すべてのお客様に、サポートされているバージョンの最新のパッチ リリースにアップグレードすることを強くお勧めします。GitLab インスタンスを保護するためのベスト プラクティスの詳細については、当社のブログ投稿をご覧ください。
推奨されるアクション
以下に説明する問題の影響を受けるバージョンを実行しているすべてのインストールを、できるだけ早く最新バージョンにアップグレードすることを強くお勧めします。
製品の特定のデプロイメント タイプ (オムニバス、ソース コード、Helm チャートなど) が指定されていない場合は、すべてのタイプが影響を受けることを意味します。
—————————————————————-
（原文）
Learn more about GitLab Patch Release: 17.5.1, 17.4.3, 17.3.6 for GitLab Community Edition (CE) and Enterprise Edition (EE).
Today we are releasing versions 17.5.1, 17.4.3, 17.3.6 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
Injection of Network Error Logging (NEL) headers in kubernetes proxy response could lead to ATO abusing OAuth flows
An issue was discovered in GitLab CE/EE affecting all versions starting from 16.1 before 17.4.6, starting from 17.5 before 17.5.4, and starting from 17.6 before 17.6.2, injection of Network Error Logging (NEL) headers in kubernetes proxy response could lead to session data exfiltration. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 8.7). It is now mitigated in the latest release and is assigned CVE-2024-11274.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Denial of Service by repeatedly sending unauthenticated requests for diff-files
An issue has been discovered in GitLab CE/EE affecting all versions from 9.4 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. An attacker could cause a denial of service with requests for diff files on a commit or merge request. This is a high severity issue (CVSS:3.1/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-8233.
Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program.
CI_JOB_TOKEN could be used to obtain GitLab session
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7 before 17.4.6, from 17.5 before 17.5.4, and from 17.6 before 17.6.2. It may have been possible for an attacker with a victim’s CI_JOB_TOKEN to obtain a GitLab session token belonging to the victim. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L, 6.7). It is now mitigated in the latest release and is assigned CVE-2024-12570.
Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program.
Open redirect in releases API
An issue was discovered in GitLab CE/EE affecting all versions from 11.8 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. An attacker could potentially perform an open redirect against a given releases API endpoint. 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-2024-9387.
Thanks swiftee for reporting this vulnerability through our HackerOne bug bounty program.
Client-Side Path Traversal in Harbor artifact links
An issue was discovered in GitLab affecting all versions starting 15.2 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. On self hosted installs, it was possible to leak the cross site request forgery (CSRF) token to an external site while the Harbor integration was enabled. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, 5.4). It is now mitigated in the latest release and is assigned CVE-2024-8647.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
HTML injection in vulnerability details could lead to Cross Site Scripting
An issue has been discovered in GitLab CE/EE affecting all versions from 17.3 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. Improper output encoding could lead to Cross Site Scripting (XSS) if Content Security Policy (CSP) is not enabled. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, 5.4). It is now mitigated in the latest release and is assigned CVE-2024-8179.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Leak branch names of projects with confidential repository
An issue has been discovered in GitLab CE/EE affecting all versions from 16.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. By using a specific GraphQL query, under specific conditions an unauthorised user can retrieve branch names. 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-2024-8116.
Thanks shells3c for reporting this vulnerability through our HackerOne bug bounty program.
Non member can view unresolved threads marked as internal notes
An issue was discovered in GitLab CE/EE affecting all versions from 15.0 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2 that allowed non-member users to view unresolved threads marked as internal notes in public projects merge requests. 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-2024-8650.
Thanks salh4ckr for reporting this vulnerability through our HackerOne bug bounty program.
Uncontrolled Resource Consumption through a maliciously crafted file
An issue was discovered in GitLab CE/EE affecting all versions starting from 13.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2, that allows an attacker to cause uncontrolled resource consumption, potentially leading to a Denial of Service (DoS) condition while parsing templates to generate changelogs. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, 4.3). It is now mitigated in the latest release and is assigned CVE-2024-9367.
Thanks l33thaxor for reporting this vulnerability through our HackerOne bug bounty program.
Certain sensitive information passed as literals inside GraphQL mutations retained in GraphQL logs
An issue was discovered in GitLab CE/EE affecting all versions starting from 11.0 before 17.4.6, starting from 17.5 before 17.5.4, and starting from 17.6 before 17.6.2, where sensitive information passed in GraphQL mutations may have been retained in GraphQL logs. This is a medium severity issue (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 4.0). It is now mitigated in the latest release and is assigned CVE-2024-12292.
This issue was discovered internally by GitLab team member Radamanthus Batnag.
Information disclosure of confidential incidents details to a group member in Gitlab Wiki
An issue has been discovered in GitLab EE affecting all versions starting from 14.3 before 17.4.6, all versions starting from 17.5 before 17.5.4 all versions starting from 17.6 before 17.6.2, that allows group users to view confidential incident title through the Wiki History Diff feature, potentially leading to information disclosure. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N, 3.1). It is now mitigated in the latest release and is assigned CVE-2024-10043.
Thanks mateuszek for reporting this vulnerability through our HackerOne bug bounty program.
Domain Confusion in GitLab Pages Unique Domain Implementation
An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.3 before 17.4.2, all versions starting from 17.5 before 17.5.4, all versions starting from 17.6 before 17.6.2. This issue allows an attacker to create a group with a name matching an existing unique Pages domain, potentially leading to domain confusion attacks. This is a low severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L, 3.1). It is now mitigated in the latest release and is assigned CVE-2024-9633.
Thanks psycho_012 for reporting this vulnerability through our HackerOne bug bounty program.
Bug fixes
17.6.2
- Upgrade to Postgres 16.6 for client libraries, openssl 3.2
- Fix 401 errors when installing the GitLab for Jira app
- Backport ‘dattang/allow-release-environments-to-fail’ to 17.6
- Backport ‘always-build-qa-image-for-release-environments’ to 17.6
- Add guard clause to Wiki#find_page when title is nil
- Merge branch ‘498768-graphql-subscriptions-ignore-unauthorized-error’ into ’17-6-stable-ee’
- Merge branch ‘nd/fix-progressbar-progress’ into ‘master’
- Backport 17-6 Remove unused matched_lines_count
- Backport Zoekt indices without zoekt_repositories stuck in initializing
- Backport ‘Zoekt: Do not process failed repos’ into 17.6
- Bump devfile gem to 0.1.1
17.5.4
- Upgrade to Postgres 16.6 for client libraries, openssl 3.2
- Fix 401 errors when installing the GitLab for Jira app
- Backport ‘always-build-qa-image-for-release-environments’ to 17.5
- Merge branch ‘498768-graphql-subscriptions-ignore-unauthorized-error’ into ’17-5-stable-ee’
- Backport https://gitlab.com/gitlab-org/gitlab/-/merge_requests/170141 into 17.5
- Quarantine Custom model features specs
17.4.6
- Upgrade to Postgres 16.6 for client libraries, openssl 3.2
- Add param filtering to avoid error while saving project settings
- Fix 401 errors when installing the GitLab for Jira app
- Backport ‘always-build-qa-image-for-release-environments’ to 17.4
- Backport fix for flaky tests in search_results spec
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製品または本サイトについては以下よりお問い合わせ下さい。
