CVE-2020-29662
published 2021-02-02CVE-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.
PriorityP427medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
0.72%
49.3th percentile
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.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | goharbor_harbor | >= 0 < 2.0.5 | 2.0.5 |
| github.com | goharbor_harbor | >= 0 < 2.0.5+incompatible | 2.0.5+incompatible |
| github.com | goharbor_harbor | >= 2.1.0 < 2.1.2 | 2.1.2 |
| github.com | goharbor_harbor | >= 2.1.0+incompatible < 2.1.2+incompatible | 2.1.2+incompatible |
| linuxfoundation | harbor | >= 2.0 < 2.0.5 | 2.0.5 |
| linuxfoundation | harbor | >= 2.1.0 < 2.1.2 | 2.1.2 |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
ghsa5.3MEDIUM
osv5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor
osv·2024-08-21
CVE-2020-29662 "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
"catalog's registry v2 api exposed on unauthenticated path in Harbor" in github.com/goharbor/harbor
OSV
"catalog's registry v2 api exposed on unauthenticated path in Harbor"
osv·2022-02-12·CVSS 5.3
CVE-2020-29662 [MEDIUM] "catalog's registry v2 api exposed on unauthenticated path in Harbor"
"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
GHSA
"catalog's registry v2 api exposed on unauthenticated path in Harbor"
ghsa·2022-02-12·CVSS 5.3
CVE-2020-29662 [MEDIUM] CWE-287 "catalog's registry v2 api exposed on unauthenticated path in Harbor"
"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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2021-02-02
Published