CVE-2020-29662
"catalog's registry v2 api exposed on unauthenticated path in Harbor"
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2020-29662- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:P/I:N/A:N - Weakness
- CWE-319
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2020-29662- Updated
- 2026-11-02
EUVDEUVD-2022-0783 No score
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.
- Record
EUVD-2022-0783- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-38r5-34mr-mvm7
"catalog's registry v2 api exposed on unauthenticated path in Harbor"
Impact
Javier Provecho, member of the TCCT (Telefonica Cloud & Cybersecurity Tech better known as ElevenPaths) SRE team discovered a vulnerability regarding Harbor’s v2 API.
The catalog’s registry v2 api is exposed on an unauthenticated path. The current catalog API path is served at the following path and it requires to be authenticated as an admin.
"GET /v2/_catalog"
However, the authorization can be bypassed by using the following path
"GET /v2/_catalog/"
Patches
If your product uses the affected releases of Harbor, update to either version v2.1.2 or v2.0.5 to fix this issue immediately
https://github.com/goharbor/harbor/releases/tag/v2.1.2 https://github.com/goharbor/harbor/releases/tag/v2.0.5
Workarounds
If you cannot access a patched release, it can be mitigated by disabling that API. For example, redirecting it to a 404 sink hole in the ingress.
For more information
If you have any questions or comments about this advisory, contact [email protected] View our security policy at https://github.com/goharbor/harbor/security/policy https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662
- Record
GHSA-38r5-34mr-mvm7- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-287, CWE-319
- Updated
- 2026-11-02
OSV
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.
- Record
CVE-2020-29662- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
OSVGHSA-38r5-34mr-mvm7
"catalog's registry v2 api exposed on unauthenticated path in Harbor"
Impact
Javier Provecho, member of the TCCT (Telefonica Cloud & Cybersecurity Tech better known as ElevenPaths) SRE team discovered a vulnerability regarding Harbor’s v2 API.
The catalog’s registry v2 api is exposed on an unauthenticated path. The current catalog API path is served at the following path and it requires to be authenticated as an admin.
"GET /v2/_catalog"
However, the authorization can be bypassed by using the following path
"GET /v2/_catalog/"
Patches
If your product uses the affected releases of Harbor, update to either version v2.1.2 or v2.0.5 to fix this issue immediately
https://github.com/goharbor/harbor/releases/tag/v2.1.2 https://github.com/goharbor/harbor/releases/tag/v2.0.5
Workarounds
If you cannot access a patched release, it can be mitigated by disabling that API. For example, redirecting it to a 404 sink hole in the ingress.
For more information
If you have any questions or comments about this advisory, contact [email protected] View our security policy at https://github.com/goharbor/harbor/security/policy https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662
- Record
GHSA-38r5-34mr-mvm7- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-287, CWE-319
- Updated
- 2026-11-02
OSVBIT-harbor-2020-29662 No score
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.
- Record
BIT-harbor-2020-29662- Updated
- 2026-11-02
OSVGO-2022-0785 No score
"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor
"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor
- Record
GO-2022-0785- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/goharbor/harborGo |
before 2.0.5 | 2.0.5 |
github.com/goharbor/harborGo |
2.1.0 up to 2.1.2 | 2.1.2 |
harborBitnami |
2.0.0 up to 2.0.5, 2.1.0 up to 2.1.2 | 2.0.52.1.2 |
github.com/goharbor/harborGo |
before 2.0.5+incompatible, 2.1.0+incompatible up to 2.1.2+incompatible | 2.0.5+incompatible2.1.2+incompatible |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-29662 is a medium vulnerability (CVSS 5.3) in Linuxfoundation Harbor, published February 2, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.73%, the 54th percentile. Fixed in github.com/goharbor/harbor 2.0.5.
References
github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7
nvd.nist.gov/vuln/detail/CVE-2020-29662