CVE-2024-5655: Improper Access Control in GitLab

Published Jun 26, 2024
·
Updated

An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows an attacker to trigger a pipeline as another user under certain circumstances.

Other sources

An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which could allow an attacker to trigger a pipeline as another user under certain circumstances. 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 resolved in the latest release and is assigned CVE-2024-5655.

— GitLab

Affected Software

7 affected componentsFixes available
GitLab GitLab>=15.8.0<16.11.5
GitLab GitLab>=15.8.0<16.11.5
GitLab GitLab>=17.0.0<17.0.3
GitLab GitLab>=17.0.0<17.0.3
GitLab GitLab=17.1.0
GitLab GitLab=17.1.0
GitLab GitLab>=15.8<16.11.5, >=17.0<17.0.3, >=17.1<17.1.1
16.11.517.0.317.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 17.1.1
  2. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 17.0.3
  3. Upgrade

    Upgrade GitLab CE/EE to a version that resolves this vulnerability.

    Fixed in 16.11.5

Event History

Jun 26, 2024
CVE Published
via MITRE·11:30 PM
Data Sourced
via MITRE·11:30 PM
RemedyDescriptionSeverityWeakness
Jun 27, 2024
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
News Published
via BleepingComputer·02:53 PM
News Published
via BleepingComputer·02:54 PM
Jul 10, 2024
News Published
via BleepingComputer·08:08 PM
Sep 12, 2024
News Published
via BleepingComputer·02:50 PM
Oct 10, 2024
News Published
via BleepingComputer·03:12 PM
Apr 22, 2026
Data Sourced
via GitLab·08:55 AM
Description

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-5655?

CVE-2024-5655 has been classified as a critical vulnerability due to its potential to allow unauthorized users to trigger pipelines.

2

How do I fix CVE-2024-5655?

To fix CVE-2024-5655, upgrade GitLab to version 16.11.5 or later, or 17.0.3 or later, or 17.1.1 or later.

3

Which versions are affected by CVE-2024-5655?

CVE-2024-5655 affects GitLab CE/EE versions from 15.8 up to 16.11.4, from 17.0 up to 17.0.2, and the exact version 17.1.0.

4

What is the impact of CVE-2024-5655?

The impact of CVE-2024-5655 allows attackers to trigger pipelines as another user, which can lead to unauthorized actions within the GitLab environment.

5

Is there a workaround for CVE-2024-5655?

There are currently no documented workarounds for CVE-2024-5655, and upgrading is the recommended action.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203