CVE-2020-29662
mediumpriority · track · 21OT risk · elevatedEPSS 0.007 · 54 %ileEUUSEPSS · scored 2026-10-28
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (9)
Products and version ranges known to be affected.
- Go github.com/goharbor/harbor2.1.0+incompatible → 2.1.2+incompatibleosvUSpkg:golang/github.com/goharbor/harbor
advisories (3)
Vendor and ecosystem advisories describing this.
- GHSA-38r5-34mr-mvm7"catalog's registry v2 api exposed on unauthenticated path in Harbor"2022-02-12ghsa · osvUS
### **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 cncf-harbor-security@lists.cncf.io View our security policy at https://github.com/goharbor/harbor/security/policy https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29662
- BIT-harbor-2020-296622024-03-06vendor · osvUS
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.
- GO-2022-0785"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor2024-08-21vendor · osvUS
"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor
also known as (6)
Other names and identifiers for this entity.
- CNNVD-202102-177cnnvd
- EUVD-2022-0783enisa_euvd
- GHSA-38r5-34mr-mvm7enisa_euvd
- BIT-harbor-2020-29662osv
- GHSA-38r5-34mr-mvm7osv
- GO-2022-0785osv
sources
Which sources assert this record, and when.
references (4)
External citations — patches, advisories, analysis.
- https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7cnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2020-29662cnnvd
- https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7enisa_euvd
- https://github.com/goharbor/harbor/security/advisories/GHSA-38r5-34mr-mvm7Release NotesThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan