What is the severity of CVE-2024-1299?

CVE-2024-1299 is classified as a privilege escalation vulnerability.

How do I fix CVE-2024-1299?

To fix CVE-2024-1299, upgrade GitLab to version 16.8.4 or 16.9.2 or later.

Which versions of GitLab are affected by CVE-2024-1299?

CVE-2024-1299 affects GitLab versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2.

What can a user with the `manage_group_access_tokens` role do in relation to CVE-2024-1299?

A user with the `manage_group_access_tokens` role could rotate group access tokens with owner privileges, leading to potential unauthorized access.

Is there a workaround for CVE-2024-1299 if I cannot upgrade immediately?

Currently, there is no documented workaround for CVE-2024-1299, so upgrading is essential to mitigate the vulnerability.

Vulnerability/
CVE-2024-1299

high

8.1

CWE

268

7/3/2024

11/12/2024

CVE-2024-1299: Privilege Chaining in GitLab

First published: Thu Mar 07 2024(Updated: )

A privilege escalation vulnerability was discovered in GitLab affecting versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2. It was possible for a user with custom role of `manage_group_access_tokens` to rotate group access tokens with owner privileges.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=16.8.0<16.8.4
GitLab	>=16.8.0<16.8.4
GitLab	>=16.9.0<16.9.2
GitLab	>=16.9.0<16.9.2

Remedy

Upgrade to versions 16.8.4, 16.9.2 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-1299?
CVE-2024-1299 is classified as a privilege escalation vulnerability.
How do I fix CVE-2024-1299?
To fix CVE-2024-1299, upgrade GitLab to version 16.8.4 or 16.9.2 or later.
Which versions of GitLab are affected by CVE-2024-1299?
CVE-2024-1299 affects GitLab versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2.
What can a user with the `manage_group_access_tokens` role do in relation to CVE-2024-1299?
A user with the `manage_group_access_tokens` role could rotate group access tokens with owner privileges, leading to potential unauthorized access.
Is there a workaround for CVE-2024-1299 if I cannot upgrade immediately?
Currently, there is no documented workaround for CVE-2024-1299, so upgrading is essential to mitigate the vulnerability.

agent/remedy
agent/references
agent/description
agent/first-publish-date
agent/type
agent/author
agent/event
collector/mitre-cve
source/MITRE
agent/title
agent/weakness
agent/last-modified-date
agent/severity
agent/softwarecombine
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/16.8.0
version/gitlab/16.9.0

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.