CVE-2024-6385: Improper Access Control in GitLab

Published Jul 10, 2024
·
Updated

An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2, 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 versions 15.8 prior to 16.11.6, 17.0 prior to 17.0.4, and 17.1 prior to 17.1.2, which allows 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-6385.

GitLab

Affected Software

7 affected componentsFixes available
GitLab GitLab>=15.8.0<16.11.6
GitLab GitLab>=15.8.0<16.11.6
GitLab GitLab>=17.0.0<17.0.4
GitLab GitLab>=17.0.0<17.0.4
GitLab GitLab>=17.1.0<17.1.2
GitLab GitLab>=17.1.0<17.1.2
GitLab GitLab>=15.8<16.11.6, >=17.0<17.0.4, >=17.1<17.1.2
16.11.617.0.417.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.11.6Fixed in 17.0.4Fixed in 17.1.2
  2. Upgrade

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

    Fixed in 17.1.2
  3. Upgrade

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

    Fixed in 17.0.4
  4. Upgrade

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

    Fixed in 16.11.6

Event History

Jul 10, 2024
News Published
via BleepingComputer·08:08 PM
News Published
via BleepingComputer·08:09 PM
Jul 11, 2024
CVE Published
via MITRE·06:56 AM
Data Sourced
via MITRE·06:56 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:15 AM
DescriptionSeverityWeaknessAffected Software
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:52 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-6385?

CVE-2024-6385 is considered a critical vulnerability that can allow attackers to trigger pipelines as another user.

2

How do I fix CVE-2024-6385?

To fix CVE-2024-6385, upgrade GitLab to version 16.11.6 or later, or to version 17.0.4 or later, or to version 17.1.2 or later.

3

What versions of GitLab are affected by CVE-2024-6385?

CVE-2024-6385 affects GitLab CE/EE versions from 15.8 up to but not including 16.11.6, from 17.0 up to but not including 17.0.4, and from 17.1 up to but not including 17.1.2.

4

Can CVE-2024-6385 be exploited remotely?

Yes, CVE-2024-6385 can be exploited remotely under certain conditions by an attacker.

5

What impact does CVE-2024-6385 have on GitLab installations?

Exploitation of CVE-2024-6385 can allow an attacker to run pipelines with the permissions of another user, potentially leading to unauthorized actions within the GitLab environment.

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