GHSA-38r5-34mr-mvm7

ghsaUSosv

"catalog's registry v2 api exposed on unauthenticated path in Harbor"

view advisory published 2022-02-12Licence: CC-BY-4.0

### **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

01

describes (1)

Related CVEs.

IDseverity exploitable
CVE-2020-29662USmedium5.3OT elevated—
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.
02

references

External citations — patches, advisories, analysis.

scry

Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.

Free scan