Threat Intelligence Database

GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.

A path traversal vulnerability in GitLab CE/EE versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 could allow an authenticated user to execute remote code via the package registry. This issue has been remediated in the specified fixed versions.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation.

A vulnerability in GitLab CE/EE versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling. This issue has been remediated in the specified versions.

A race condition vulnerability in GitLab Enterprise Edition versions 17.0 up to but not including 19.0.5, 19.1 up to 19.1.3, and 19.2 up to 19.2.1 could allow an authenticated user to merge code into a protected branch without the required approvals. This issue arises from a time-of-check to time-of-use (TOCTOU) flaw in the approval rule processing logic. The vulnerability has been remediated in fixed versions.

A vulnerability in GitLab CE/EE versions from 14.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows an attacker to execute arbitrary JavaScript in another user's browser via a crafted URL. This occurs due to improper sanitization of user-controlled input, leading to a cross-site scripting (XSS) issue. The vulnerability has been remediated in the specified fixed versions.

A vulnerability in GitLab CE/EE versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows an authenticated user with Maintainer role to modify protected branch configurations due to improper authorization in a project API endpoint. This issue has been remediated by GitLab in the specified fixed versions.

A vulnerability in GitLab CE/EE versions from 10.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allowed an authenticated user with developer-role permissions to commit changes to a project even after being removed as a member. This was due to improper authorization checks on merge request collaboration settings. The issue has been remediated in the specified fixed versions.

A vulnerability in GitLab CE/EE versions from 11.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow an unauthenticated user to cause a denial of service. The issue arises from insufficient resource throttling when processing merge request discussions. This vulnerability has been remediated in the specified fixed versions.