GitLab CE/EE vulnerabilities

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. This issue could have allowed an unauthenticated user to cause denial of service by sending specially crafted requests due to insufficient input validation.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. This issue could have allowed an unauthenticated user to cause denial of service by sending specially crafted JSON payloads due to insufficient input validation.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. This issue could have allowed an unauthenticated user to cause denial of service by sending specially crafted payloads on certain API endpoints.

GitLab CE/EE versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 contain an integer overflow issue when compiling a specially crafted regular expression in a CI/CD configuration. Under certain conditions an authenticated user could execute arbitrary code on the GitLab server.

GitLab CE/EE versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 contain a double free issue when parsing a specially crafted regular expression in a CI/CD configuration. Under certain conditions an authenticated user could execute arbitrary code on the GitLab server.

An issue has been discovered in GitLab CE/EE affecting all versions from 8.14 before 16.0.8, from 16.1 before 16.1.3, and from 16.2 before 16.2.2. A Denial of Service (DoS) attack was possible via crafted payloads using AutolinkFilter at the preview_markdown endpoint.

A vulnerability in GitLab CE/EE could, under certain conditions, allow an authenticated user to execute arbitrary JavaScript in the context of other users' browser sessions via a specially crafted repository. Affects versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2.

GitLab CE/EE versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a fixed issue that, under certain conditions, could allow an unauthenticated user to read internal notes and confidential system notes on public projects due to improper authorization in the GraphQL API.

GitLab CE/EE versions from 17.11 before 19.2.8, all 19.3 versions, and 19.4 before 19.4.2 have a fixed issue that, under certain conditions, could allow an unauthenticated user to read work item contents from private groups and projects due to incorrect authorization checks.

GitLab CE/EE versions from 18.9 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a vulnerability that, under certain conditions, could allow an authenticated user with a fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token's intended scope, due to incorrect authorization of the import target namespace.

GitLab CE/EE versions from 13.11 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a fixed issue that, under certain conditions, could allow an authenticated user controlling a Kubernetes agent to cause sensitive authentication tokens to be sent to an unintended server due to improper redirect validation in the Kubernetes proxy.

GitLab CE/EE versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a fixed issue that, under certain conditions, could allow an authenticated user holding a project-scoped fine-grained Personal Access Token to modify integrations belonging to a group outside the token's scope, due to incorrect authorization checks.

GitLab CE/EE versions from 13.8 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a fixed issue that, under certain conditions, could allow an authenticated user with reporter role to access restricted CI artifact report content they were not authorized to, due to missing authorization checks.

GitLab CE/EE versions from 15.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a fixed issue that, under certain conditions, could allow a user to download package files from a public project due to improper authorization checks.

A vulnerability in GitLab CE/EE could, under certain conditions, allow an authenticated user with Developer role to execute CI/CD pipelines on protected branches without authorization. Affects versions from 18.7 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2.

A vulnerability in GitLab CE/EE could, under certain conditions, allow a user to poison cached responses for raw repository files, causing targeted users' CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables. Affects versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2.

GitLab CE/EE versions from 17.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 have a vulnerability that, under certain conditions, could allow an authenticated user with maintainer-role permissions to remove certain package registry metadata that package protection rules restrict to higher roles, due to improper authorization checks.

GitLab CE/EE contains a flaw in cache key construction that, under certain deployment configurations, allows an authenticated user to poison cached page content served to other users. Affected versions are from 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2.

GitLab CE/EE contains a server-side request forgery (SSRF) vulnerability caused by a time-of-check to time-of-use race condition in URL validation during repository import operations. An authenticated user could, under certain conditions, reach internal network resources.

GitLab CE/EE contains a race condition in the MCP search tool's shared state handling that could cause search results to be returned under an incorrect user context. Affected versions are from 18.6 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user to prevent another user from modifying their group settings due to improper validation of group URL slugs during namespace transfers.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.9 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that an authenticated user with developer-role permissions could substitute package file content and hide packages from their owners due to improper authorization checks in the Generic Package Registry.

GitLab CE/EE has an improper authorization issue on internal data emission endpoints that, under certain conditions, allows an authenticated user to access sensitive credentials and tokens without transiting the expected proxy. Affected versions are from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2.

GitLab CE/EE versions from 15.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 contain a vulnerability that under certain conditions allows an authenticated user to access CI/CD variables outside their intended environment scope. The cause is improper input validation in the environment scope pattern matcher.

A missing authorization check in GitLab CE/EE allows an unauthorized user to view project import source information. Affected versions are from 16.6 to 19.0.4, 19.1 to 19.1.2, and 19.2 to 19.2.0.

GitLab CE/EE has improper authorization checks on merge request collaboration settings, allowing an authenticated user with developer role to commit changes to a project after being removed as a member. Affected versions are 10.6 through 19.0.4, 19.1 through 19.1.2, and 19.2 through 19.2.0.

A vulnerability in GitLab CE/EE allowed an unauthenticated user to view confidential issue references in public projects under certain conditions due to improper authorization checks. Affected versions: 17.5 to 18.11.6, 19.0 to 19.0.3, and 19.1 to 19.1.1.

A vulnerability in GitLab CE/EE allows an authenticated user to conceal content within a Snippet due to improper input validation. The issue affects versions from 14.8 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1.

A vulnerability in GitLab CE/EE allows an authenticated user with maintainer role to make requests to internal network resources via mirror synchronization due to improper URL validation. Affected versions: from 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1.

A vulnerability in GitLab CE/EE allows an unauthenticated attacker to execute arbitrary JavaScript in a user's browser session due to improper path validation. Affects versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, an unauthenticated user could impersonate the GitLab Support Bot and inject arbitrary content via a specially crafted Service Desk email reply due to improper neutralization in email template processing.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, an authenticated user could read arbitrary files from the Gitaly server and access internal network resources during repository import, due to insufficient validation of secondary URLs.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, this could have allowed an unauthenticated user to cause denial of service due to improper input validation in the API request parsing middleware.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, an authenticated user with developer-role permissions could hide changes from merge request diff views due to improper input handling of file names.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, an authenticated user with developer-role permissions could modify hidden merge requests due to incorrect authorization enforcements.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, this could have allowed an authenticated user to access confidential issue details due to incorrect authorization checks.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. Under certain conditions, an authenticated user could have caused denial of service due to uncontrolled resource consumption when processing a specially crafted file upload.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. This issue could have allowed an authenticated user to cause denial of service on the CI/CD Catalog page due to improper sanitization.

GitLab CE/EE from versions 18.2 to 18.8.9, 18.9 to 18.9.5, and 18.10 to 18.10.3 contains a vulnerability that allows an authenticated user to access confidential issues assigned to other users via CSV export due to insufficient authorization checks.

An issue has been discovered in GitLab CE/EE affecting all versions from 11.8 to 16.1.5, from 16.2 to 16.2.5, and from 16.3 to 16.3.1. A malicious Maintainer can, under specific circumstances, leak the Sentry token by changing the configured URL in the Sentry error tracking settings page.

An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.9 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. It was possible to takeover GitLab Pages with unique domain URLs if the random string added was known.

An issue has been discovered in GitLab CE/EE affecting all versions from 9.3 before 16.0.8, from 16.1 before 16.1.3, and from 16.2 before 16.2.2. A Regular Expression Denial of Service was possible via sending crafted payloads which use ProjectReferenceFilter to the preview_markdown endpoint.

An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. An invalid 'start_sha' value on merge requests page may lead to Denial of Service as Changes tab would not load.

An issue has been discovered in GitLab CE/EE affecting versions from 10.0 before 16.0.8, from 16.1 before 16.1.3, and from 16.2 before 16.2.2. A reflected XSS was possible when creating specific PlantUML diagrams, allowing attackers to perform arbitrary actions on behalf of victims.

An issue has been discovered in GitLab CE/EE that allows an attacker to merge arbitrary code into protected branches. This affects all versions starting from 15.3 before 15.11.10, all versions starting from 16.0 before 16.0.6, and all versions starting from 16.1 before 16.1.1.

An issue has been discovered in GitLab CE/EE affecting all versions from 10.3 before 15.11.10, all versions from 16.0 before 16.0.6, and all versions from 16.1 before 16.1.1. A Regular Expression Denial of Service was possible via sending crafted payloads to the preview_markdown endpoint.

An information disclosure issue in Gitlab CE/EE affects all versions from 13.6 prior to 15.11.10, all versions from 16.0 prior to 16.0.6, and all versions from 16.1 prior to 16.1.1. The issue resulted in the Sidekiq log including webhook tokens when the log format was set to 'default'.

An information disclosure issue in GitLab CE/EE affects all versions from 16.0 prior to 16.0.6, and version 16.1.0. It allows unauthenticated actors to access the import error information if a project was imported from GitHub.