CVE-2020-13794Medium· 4.3▾ SunlitAuthenticated users can exploit an enumeration vulnerability in Harbor
▾ Sunlit zone — Low / medium · no exploitation signal
impact 23.7 · likelihood 0.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 9.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.3%
Hidde Smit from Cyber Eagle has discovered an User Enumeration flaw in Harbor. The issue is present in the "/users" api endpoint. This endpoint is supposed to be restricted to administrators. This restriction is able to be bypassed and information can be obtained via the "search" functionality.
Non-administrator users (such as those created via self-registration) can list all usernames and user IDs by sending a GET request to /api/users/search with parameter "username" and value "_", as follows:
curl -X GET "https://<host>/api/users/search?username=_" -H "accept: application/json" --user <user>:<password>
The vulnerability was immediately fixed by the Harbor team and all supported versions were patched. With the patched versions of Harbor, the username is required for search and we have removed the support for querying by email.
If your product uses the affected releases of Harbor, update to either version 2.1.0 or 2.0.3 to fix this issue immediately
https://github.com/goharbor/harbor/releases/tag/v2.1.0 https://github.com/goharbor/harbor/releases/tag/v2.0.3
There is no workaround for this issue
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-13794
github.com/goharbor/harbor < 2.0.3Upgrade to a patched release:
github.com/goharbor/harbor 2.0.3Connected by shared product, vendor, weakness, or advisory.
CVE-2024-22261Low· 2.7SQL Injection in Harbor scan log API
CVE-2023-20902Medium· 5.9Harbor timing attack risk
CVE-2024-22244Medium· 4.3Open Redirect URL in Harbor
CVE-2020-29662Medium· 5.3"catalog's registry v2 api exposed on unauthenticated path in Harbor"
CVE-2026-92770Medium· 6.5Harbor through 2.15.2 fails to properly restrict the q query parameter filtering on scanner registration access credentials