First published: Tue Sep 19 2023(Updated: )
An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.2.7, all versions starting from 16.3 before 16.3.4. It was possible for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies. This was a bypass of [CVE-2023-3932](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3932) showing additional impact.
Credit: cve@gitlab.com cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab GitLab | >=13.12<16.2.7 | |
GitLab GitLab | >=16.3<16.3.4 | |
>=13.12<16.2.7 | ||
>=16.3<16.3.4 |
Upgrade to versions 16.2.7, 16.3.4 or above For those users unable to upgrade for those versions, you can mitigate the vulnerability by having at most one of those two features turned on at one time: - [Direct transfers](https://docs.gitlab.com/ee/administration/settings/import_and_export_settings.html#enable-migration-of-groups-and-projects-by-direct-transfer) - [Security policies](https://docs.gitlab.com/ee/user/application_security/policies/scan-execution-policies.html)
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-5009 is a vulnerability discovered in GitLab EE affecting all versions starting from 13.12 before 16.2.7.
CVE-2023-5009 has a severity rating of 9.6, which is classified as critical.
CVE-2023-5009 allows an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies.
If your GitLab EE version is between 13.12 and 16.2.7, or between 16.3 and 16.3.4, it is affected by CVE-2023-5009.
To mitigate CVE-2023-5009, you should update to GitLab EE version 16.2.7 or higher, or version 16.3.4 or higher.