GitLab EE vulnerabilities

GitLab EE versions from 10.6 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1 contain a flaw allowing an authenticated attacker to trigger unauthorized pipeline executions by manipulating commits.

In GitLab EE versions 18.3 to 18.3.4 and 18.4 to 18.4.2, incorrectly scoped GraphQL mutations allow authenticated users with read-only API tokens to perform unauthorized write operations on vulnerability records.

A vulnerability was discovered in GitLab EE affecting all versions from 16.6 before 18.2.7, 18.3 before 18.3.3, and 18.4 before 18.4.1. Project Maintainers can assign custom roles to users with permissions exceeding their own, effectively granting themselves elevated privileges.

An information disclosure issue in GitLab EE affecting all versions from 16.2 prior to 16.2.5, and 16.3 prior to 16.3.1 allowed other Group Owners to see the Public Key for a Google Cloud Logging audit event streaming destination, if configured.

An issue has been discovered in GitLab EE affecting all versions from 16.1 to 16.1.5, from 16.2 to 16.2.5, and from 16.3 to 16.3.1. An external user with an owner role in a group may escalate their privileges by creating a service account in that group.

An issue has been discovered in GitLab EE affecting all versions from 14.1 before 16.0.8, from 16.1 before 16.1.3, and from 16.2 before 16.2.2. EE-licensed users could link any security policy project by its ID to projects or groups they have access to, potentially revealing the security project's configured security policies.

An issue has been discovered in GitLab EE affecting all versions starting from 13.12 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 for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies.

An issue has been discovered in GitLab EE affecting all versions from 15.11 prior to 16.2.2 which allows an attacker to spike the resource consumption resulting in DoS.

An issue has been discovered in GitLab EE affecting all versions starting from 14.3 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. Access tokens may have been logged when a query was made to a specific endpoint.

A sensitive information leak issue has been discovered in GitLab EE affecting all versions from 16.0 to 16.0.6 and from 16.1 to 16.1.1. It allows access to titles of private issues and MRs.

An issue has been discovered in GitLab EE affecting all versions starting from 12.8 before 15.11.11, all versions starting from 16.0 before 16.0.7, all versions starting from 16.1 before 16.1.2. An attacker could change the name or path of a public top-level group in certain situations.