===================================================================== CERT-Renater Note d'Information No. 2023/VULN451 _____________________________________________________________________ DATE : 06/11/2023 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running GitLab versions prior to 16.5.1, 16.4.2, 16.3.6. ===================================================================== https://about.gitlab.com/releases/2023/10/31/security-release-gitlab-16-5-1-16-4-2-16-3-6-released/ _____________________________________________________________________ GitLab Security Release: 16.5.1, 16.4.2, 16.3.6 Learn more about GitLab Security Release: 16.5.1, 16.4.2, 16.3.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). Today we are releasing versions 16.5.1, 16.4.2, 16.3.6 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 3rd Thursday 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. On 2023-10-20 11:03 UTC, GitLab internally discovered (CVE-2023-5831) that a change in the GitLab sidebar feature resulted in self-managed GitLab instances sending version-checks to version.gitlab.com each time they opened a page on their GitLab instance. This means that the hostnames and current versions of self-managed GitLab instances were being sent to version.gitlab.com any time a user of that GitLab instance opened any page, regardless of whether or not the sending of version-check was enabled. This information was only accessible to some GitLab team members and was not exposed externally, and GitLab is working to purge the erroneously collected data from our database. 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 Disclosure of CI/CD variables using Custom project templates Medium GitLab omnibus DoS crash via OOM with CI Catalogs Medium Parsing gitlab-ci.yml with large string via timeout input leads to Denial of Service Medium DoS - Blocking FIFO files in Tar archives Medium Titles exposed by service-desk template Medium Approval on protected environments can be bypassed Low Version information disclosure when super_sidebar_logged_out feature flag is enabled Low Add abuse detection for search syntax filter pipes Low Disclosure of CI/CD variables using Custom project templates An issue has been discovered in GitLab affecting all versions starting from 11.6 before 12.9.8, all versions starting from 12.10 before 12.10.7, all versions starting from 13.0 before 13.0.1. It was possible for an unauthorised project or group member to read the CI/CD variables using the custom project templates. 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-2023-3399. Thanks theluci for reporting this vulnerability through our HackerOne bug bounty program. GitLab omnibus DoS crash via OOM with CI Catalogs An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.2 before 16.3.6, all versions starting from 16.4 before 16.4.2, all versions starting from 16.5 before 16.5.1. A low-privileged attacker can point a CI/CD Component to an incorrect path and cause the server to exhaust all available memory through an infinite loop and cause Denial of Service. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2023-5825. Thanks blakbat for reporting this vulnerability through our HackerOne bug bounty program" Parsing gitlab-ci.yml with large string via timeout input leads to Denial of Service An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.3 before 16.3.6, all versions starting from 16.4 before 16.4.2, all versions starting from 16.5 before 16.5.1. A Regular Expression Denial of Service was possible by adding a large string in timeout input in gitlab-ci.yml file." 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-2023-3909. Thanks akadrian for reporting this vulnerability through our HackerOne bug bounty program. DoS - Blocking FIFO files in Tar archives An issue has been discovered in GitLab EE/CE affecting all versions starting before 16.3.6, all versions starting from 16.4 before 16.4.2, all versions starting from 16.5 before 16.5.1 which allows an attackers to block Sidekiq job processor. 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-2023-3246. Thanks zhutyra for reporting this vulnerability through our HackerOne bug bounty program. Titles exposed by service-desk template An issue has been discovered in GitLab EE affecting all versions starting from 16.0 before 16.3.6, all versions starting from 16.4 before 16.4.2, all versions starting from 16.5 before 16.5.1. Arbitrary access to the titles of an private specific references could be leaked through the service-desk custom email template. 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-2023-5600. Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program. Approval on protected environments can be bypassed An authorization issue affecting GitLab EE affecting all versions from 14.7 prior to 16.3.6, 16.4 prior to 16.4.2, and 16.5 prior to 16.5.1, allowed a user to run jobs in protected environments, bypassing any required approvals. 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-2023-4700. Thanks Gregor Pirolt for reporting this vulnerability through our HackerOne bug bounty program. Version information disclosure when super_sidebar_logged_out feature flag is enabled An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.0 before 16.3.6, all versions starting from 16.4 before 16.4.2, and all versions starting from 16.5.0 before 16.5.1 which have the super_sidebar_logged_out feature flag enabled. Affected versions with this default-disabled feature flag enabled may unintentionally disclose GitLab version metadata to unauthorized actors. 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-2023-5831. This vulnerability was discovered internally by the GitLab team. Add abuse detection for search syntax filter pipes An issue has been discovered in GitLab EE with Advanced Search affecting all versions from 13.9 to 16.3.6, 16.4 prior to 16.4.2 and 16.5 prior to 16.5.1 that could allow a denial of service in the Advanced Search function by chaining too many syntax operators. 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. We have requested a CVE ID and will update this blog post when it is assigned. This vulnerability was found internally by GitLab. Update curl to v8.4.0 curl has been updated to v8.4.0 to mitigate CVE-2023-38545. Update mermaid to 10.5.0 mermaid has been updated to 10.5.0 to mitigate a security issue. Patch NGINX for CVE-2023-44487 NGINX has been patched to mitigate CVE-2023-44487. Non Security Patches 16.5.1 Revert better-error-messages-for-pull-mirroring Update post migration to drop column only if it exists Downgrade vue-apollo to prevent auto-restarting subscriptions on error 16.4.2 UBI: Explicitly add webrick gem to mailroom build Update VERSION files Update dependency prometheus-client-mmap to '>= 0.28.1' Backport: fix migration when commit_message_negative_regex is missing Backport to 16.4: Geo: Avoid getting resources stuck in Queued Fix pipeline schedules view when owner is nil Quarantine flaky delete_job_spec:46 Create Geo event when project is created Fix bug with batched gitaly ref deletion duplicates 16.3.6 UBI: Explicitly add webrick gem to mailroom build Backport 16.3: Upgrade exiftool to 12.65 Fixes the 16-3-stable branch Backport to 16.3: Geo: Avoid getting resources stuck in Queued 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 + =========================================================