Cloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 allows resource enumeration because unauthenticated API calls reveal (via the HTTP status code) whether a resource exists.
euvd · EUVD-2022-1148 · Published
No access to your tenant or devices. Every item links to its source. What this means
Cloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 allows resource enumeration because unauthenticated API calls reveal (via the HTTP status code) whether a resource exists.
Read the publisher's advisoryCloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 allows resource enumeration because unauthenticated API calls reveal (via the HTTP status code) whether a resource exists.
Read the publisher's advisoryCloud Native Computing Foundation Harbor before 1.10.3 and 2.x before 2.0.1 allows resource enumeration because unauthenticated API calls reveal (via the HTTP status code) whether a resource exists.
Read the publisher's advisory# Impact Sean Wright from Secureworks has discovered an enumeration vulnerability. An attacker can make use of the Harbor API to make unauthenticated calls to the Harbor instance. Based on the HTTP status code in the response, an attacker is then able to work out which resources exist, and which do not. This would likely be accomplished by either providing a wordlist or enumerating through a sequence an unauthenticated attacker is able to enumerate resources on the system. This provides them with information such as existing projects, repositories, etc. The vulnerability was immediately fixed by the Harbor team. # Issue The following API resources where found to be vulnerable to enumeration attacks: /api/chartrepo/{repo}/prov (POST) /api/chartrepo/{repo}/charts (GET, POST) /api/chartrepo/{repo}/charts/{name} (GET, DELETE) /api/chartrepo/{repo}/charts/{name}/{version} (GET, DELETE) /api/labels?name={name}&scope=p (GET) /api/repositories?project_id={id} (GET) /api/repositories/{repo_name}/ (GET, PUT, DELETE) /api/repositories/{repo_name}/tags (GET) /api/repositories/{repo_name}/tags/{tag}/manifest?version={version} (GET) /api/repositories/{repo_name/{tag}/labels (GET) /api/projects?project_name={name} (HEAD) /api/projects/{project_id}/summary (GET) /api/projects/{project_id}/logs (GET) /api/projects/{project_id} (GET, PUT, DELETE) /api/projects/{project_id}/metadatas (GET, POST) /api/projects/{project_id}/metadatas/{metadata_name} (GET, PUT) # Known Attack Vectors Successful exploitation of this issue will lead to bad actors identifying which resources exist in Harbor without requiring authentication for the Harbor API. # Patches If your product uses the affected releases of Harbor, update to version 1.10.3 or 2.0.1 to patch this issue immediately. https://github.com/goharbor/harbor/releases/tag/v1.10.3 https://github.com/goharbor/harbor/releases/tag/v2.0.1 # Workarounds There is no known workaround # 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
Read the publisher's advisoryUnauthenticated users can exploit an enumeration vulnerability in Harbor (CVE-2019-19030) in github.com/goharbor/harbor
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
euvd · EUVD-2022-1148 · Published
nvd · CVE-2019-19030 · Published
osv · GHSA-q9x4-q76f-5h5j · Published
osv · GO-2022-0704 · Published
cve-program · CVE-2019-19030 · Published