Ce mail provient de l'extérieur, restons vigilants ===================================================================== CERT-Renater Note d'Information No. 2025/VULN181 _____________________________________________________________________ DATE : 27/03/2025 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running GitLab versions prior to 17.10.1, 17.9.3, 17.8.6. ===================================================================== https://about.gitlab.com/releases/2025/03/26/patch-release-gitlab-17-10-1-released/ _____________________________________________________________________ GitLab Patch Release: 17.10.1, 17.9.3, 17.8.6 Learn more about GitLab Patch Release: 17.10.1, 17.9.3, 17.8.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). Today we are releasing versions 17.10.1, 17.9.3, 17.8.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 Title Severity Cross-site Scripting (XSS) through merge-request error messages High Cross-site Scripting (XSS) through improper rendering of certain file types High Admin Privileges Persists After Role is Revoked High External user can access internal projects Medium Prompt injection in Amazon Q integration may allow unauthorized actions Medium Uncontrolled Resource Consumption via a maliciously crafted terraform file in merge request Medium Maintainer can inject shell code in Harbor project name configuration when using helper scripts Low Cross-site Scripting (XSS) through merge-request error messages An issue has been discovered in Gitlab EE/CE affecting all versions from 13.5.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. Certain error messages could allow Cross-Site Scripting attacks (XSS). This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7). It is now mitigated in the latest release and is assigned CVE-2025-2255. Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program. Cross-site Scripting (XSS) through improper rendering of certain file types An issue has been discovered in GitLab CE/EE affecting all versions from 17.7 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. Improper rendering of certain file types leads to cross-site scripting. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7). It is now mitigated in the latest release and is assigned CVE-2025-0811. Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program. Admin Privileges Persists After Role is Revoked An improper access control vulnerability in GitLab CE/EE affecting all versions from 17.4 prior to 17.8.6, 17.9 prior to 17.9.3, and 17.10 prior to 17.10.1 allows a user who was an instance admin before but has since been downgraded to a regular user to continue to maintain elevated privileges to groups and projects. This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.5). It is now mitigated in the latest release and is assigned CVE-2025-2242. External user can access internal projects An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1, allowing internal users to gain unauthorized access to internal projects. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N, 5.2). It is now mitigated in the latest release and is assigned CVE-2024-12619. Thanks aituglo for reporting this vulnerability through our HackerOne bug bounty program. Prompt injection in Amazon Q integration may allow unauthorized actions An issue has been discovered in the GitLab Duo with Amazon Q affecting all versions from 17.8 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A specifically crafted issue could manipulate AI-assisted development features to potentially expose sensitive project data to unauthorized users. 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). We have requested a CVE ID and will update this blog post when it is assigned. This vulnerability has been discovered internally by GitLab team member Félix Veillette-Potvin. Uncontrolled Resource Consumption via a maliciously crafted terraform file in merge request An issue has been discovered in GitLab EE/CE affecting all versions from 12.10 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A maliciously crafted file can cause uncontrolled CPU consumption when viewing the associated merge request. 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-10307. Thanks l33thaxor for reporting this vulnerability through our HackerOne bug bounty program. Maintainer can inject shell code in Harbor project name configuration when using helper scripts An issue was discovered in GitLab EE affecting all versions starting from 14.9 before 17.8.6, all versions starting from 17.9 before 17.8.3, all versions starting from 17.10 before 17.10.1. An input validation issue in the Harbor registry integration could have allowed a maintainer to add malicious code to the CLI commands shown in the UI. This is a low severity issue (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N, 3.7). It is now mitigated in the latest release and is assigned CVE-2024-9773. Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program. Bug fixes 17.10.1 Merge branch 'fixup-non-based-ubi' into '17-10-stable' Changes for storing value of bypass_two_factor to session Correct incorrect PG version in CHANGELOG 17.9.3 Bump go to v1.23.6 Merge branch 'fixup-non-based-ubi' into '17-9-stable' 17.9 Backport: jliu/gitaly-dns-tls 17.9 backport: Update build-proto-gem [Backport 17.9] Fix frozen array error with custom analyzers Update dependency gitlab-mail_room to v0.0.27 [backport] Fixed regex and syntax options button under some conditions [17.9] Backport: Zoekt: Index pending delete projects [Backport 17.9] Update truncato gem Reorder runners backfill migrations - 17.9 backport [Backport 17.9] Replace #test-platform in favour of #s_developer_experience Update Gitaly client dependency to include DNS lookup change (backport to 17.9) Backport 'ci-internal-release-docker-branch-dev' into '17-9-stable' Backport 17.9: Update container-registry to v4.15.2-gitlab 17.8.6 UBI/FIPS: Fixup container_version when not using gitlab-base 17.8 Backport: jliu/gitaly-dns-tls Fix a spec typo in merge_requests_controller_spec Update Gitaly client dependency to include DNS lookup change (backport 17.8) [Backport 17.8] Replace #test-platform in favour of #s_developer_experience Fix SPP worker bug in 17.8 Reorder runners backfill migrations - 17.8 backport Backport 'ci-internal-release-docker-branch-dev' into '17-8-stable' 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. ========================================================= + 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 + =========================================================