{"uuid": "db9dd42d-746e-40cf-bae6-61042f0c1d48", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "name": "GitLab Critical Patch Release: 17.4.2, 17.3.5, 17.2.9", "description": "GitLab Critical Patch Release: 17.4.2, 17.3.5, 17.2.9\nNikhil George\n8\u201310 minutes\n\nLearn more about GitLab Critical Patch Release: 17.4.2, 17.3.5, 17.2.9 for GitLab Community Edition (CE) and Enterprise Edition (EE).\n\nToday we are releasing versions 17.4.2, 17.3.5, 17.2.9 for GitLab Community Edition (CE) and Enterprise Edition (EE).\n\nThese 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.\n\nGitLab 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.\n\nFor security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.\n\nWe 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.\nRecommended Action\n\nWe strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible.\n\nWhen no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected.\nSecurity fixes\nTable of security fixes\nTitle \tSeverity\nRun pipelines on arbitrary branches \tCritical\nAn attacker can impersonate arbitrary user \tHigh\nSSRF in Analytics Dashboard \tHigh\nViewing diffs of MR with conflicts can be slow \tHigh\nHTMLi in OAuth page \tHigh\nDeploy Keys can push changes to an archived repository \tMedium\nGuests can disclose project templates \tMedium\nGitLab instance version disclosed to unauthorized users \tLow\nRun pipelines on arbitrary branches\n\nAn 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.\n\nThanks pwnie for reporting this vulnerability through our HackerOne bug bounty program.\nAn attacker can impersonate arbitrary user\n\nAn 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.\n\nThanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program.\nSSRF in Analytics Dashboard\n\nAn 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.\n\nThanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.\nViewing diffs of MR with conflicts can be slow\n\nAn 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.\n\nThanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program.\nHTMLi in OAuth page\n\nA 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.\n\nThanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.\nDeploy Keys can push changes to an archived repository\n\nAn 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.\n\nThanks stevenorman for reporting this vulnerability.\nGuests can disclose project templates\n\nAn 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.\n\nThanks js_noob for reporting this vulnerability through our HackerOne bug bounty program.\nGitLab instance version disclosed to unauthorized users\n\nAn 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.\n\nThis issue was discovered internally by GitLab team member Paul Gascou-Vaillancourt.\nBug fixes\n17.4.2\n\n    Backport: fix: Specify an absolute directory for SCHEMA_VERSIONS_DIR to 17-4-stable\n    Backport grpc-go v1.67.1 upgrade to 17.4\n    Update expected vulnerability in enable_advanced_sast_spec.rb\n    Skip multi-version upgrade job for stable branch MRs\n    Backport 17.4 Fix label filter by name for search\n    Restrict duo pro assignment email to duo pro for sm\n    Drop project_id not null constraint ci_deleted_objects\n    [Backport] Go-get: fix 401 error for unauthenticated requests\n\n17.3.5\n\n    Backport: fix: Specify an absolute directory for SCHEMA_VERSIONS_DIR to 17-3-stable\n    Backport: fix: Allow non-root user to run the bundle-certificates script 17.3\n    Skip multi-version upgrade job for stable branch MRs\n    Ensure restricted visibility levels is an array - 17.3 backport\n\n17.2.9\n\n    Skip multi-version upgrade job for stable branch MRs\n    Ensure restricted visibility levels is an array - 17.2 backport\n\nUpdating\n\nTo update GitLab, see the Update page. To update Gitlab Runner, see the Updating the Runner page.\nReceive Patch Notifications\n\nTo 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.\nWe\u2019re combining patch and security releases\n\nThis 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.\n", "creation_timestamp": "2024-10-11T12:24:01.570554+00:00", "timestamp": "2024-10-11T12:24:01.570554+00:00", "related_vulnerabilities": ["CVE-2024-5005", "CVE-2024-9596", "CVE-2024-8977", "CVE-2024-9631", "CVE-2024-6530", "CVE-2024-9623", "CVE-2024-8970", "CVE-2024-9164"], "author": {"login": "adulau", "name": "Alexandre Dulaunoy", "uuid": "c933734a-9be8-4142-889e-26e95c752803"}}