Linuxfoundation Harbor vulnerabilities
24 vulnerabilities
Known vulnerabilities in Linuxfoundation Harbor, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2020-13794github.com/goharborharbor+1
EPSS score1.27%
Harbor 1.9.* 1.10.* and 2.0.* allows Exposure of Sensitive Information to an Unauthorized Actor.CVE-2020-13788github.com/goharborharbor+1EPSS score1.30%
Harbor prior to 2.0.1 allows SSRF with this limitation: an attacker with the ability to edit projects can scan ports of hosts accessible on the Harbor server's intranet.CVE-2020-29662github.com/goharborharbor+1EPSS score0.72%
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.CVE-2022-31667github.com/goharborharbor+1EPSS score0.53%
Harbor fails to validate the user permissions when updating a robot account that belongs to a project that the authenticated user doesn’t have access to.
By sending a request that attempts to update a robot account, and specifying a robot account id and robot account name that belongs to a different project that the user doesn’t have access to, it was possible to revoke the robot account permissions.CVE-2022-31668github.com/goharborharbor+2EPSS score0.30%
Harbor fails to validate the user permissions when updating p2p preheat policies. By sending a request to update a p2p preheat policy with an id that belongs to a project that the currently authenticated user doesn't have access to, the attacker could modify p2p preheat policies configured in other projects.CVE-2022-31669github.com/goharborharbor+1EPSS score0.41%
Harbor fails to validate the user permissions when updating tag immutability policies.
By sending a request to update a tag immutability policy with an id that belongs to a
project that the currently authenticated user doesn’t have access to, the attacker could
modify tag immutability policies configured in other projects.CVE-2022-31671github.com/goharborharbor+1EPSS score0.53%
Harbor fails to validate user permissions when reading and updating job execution logs through the P2P preheat execution logs. By sending a request that attempts to read/update P2P preheat execution logs and specifying different job IDs, malicious authenticated users could read all the job logs stored in the Harbor database.CVE-2022-31670github.com/goharborharbor+1EPSS score0.55%
Harbor fails to validate the user permissions when updating tag retention policies.
By sending a request to update a tag retention policy with an id that belongs to a project that the currently authenticated user doesn’t have access to, the attacker could modify
tag retention policies configured in other projects.CVE-2022-31666github.com/goharborharbor+1EPSS score0.50%
Harbor fails to validate user permissions while deleting Webhook policies, allowing malicious users to view, update and delete Webhook policies of other users. The attacker could modify Webhook policies configured in other projects.CVE-2022-46463linuxfoundationharborEPSS score6.24%
An access control issue in Harbor v1.X.X to v2.5.3 allows attackers to access public and private image repositories without authentication. NOTE: the vendor's position is that this "is clearly described in the documentation as a feature."CVE-2017-17697linuxfoundationharborEPSS score1.39%
The Ping() function in ui/api/target.go in Harbor through 1.3.0-rc4 has SSRF via the endpoint parameter to /api/targets/ping.CVE-2024-22278github.com/goharborharbor+2EPSS score0.36%
Incorrect user permission validation in Harbor <v2.9.5 and Harbor <v2.10.3 allows authenticated users to modify configurations.CVE-2024-22261github.com/goharborharbor+2EPSS score0.42%
SQL-Injection in Harbor allows priviledge users to leak the task IDsCVE-2024-22244github.com/goharborharbor+2EPSS score0.36%
Open Redirect in Harbor <=v2.8.4, <=v2.9.2, and <=v2.10.0 may redirect a user to a malicious site.CVE-2019-16919linuxfoundationharbor+2EPSS score1.71%
Harbor API has a Broken Access Control vulnerability. The vulnerability allows project administrators to use the Harbor API to create a robot account with unauthorized push and/or pull access permissions to a project they don't have access or control for. The Harbor API did not enforce the proper project permissions and project scope on the API request to create a new robot account.CVE-2019-16097github.com/goharborharbor+1EPSS score22.27%
core/api/user.go in Harbor 1.7.0 through 1.8.2 allows non-admin users to create admin accounts via the POST /api/users API, when Harbor is setup with DB as authentication backend and allow user to do self-registration. Fixed version: v1.7.6 v1.8.3. v.1.9.0. Workaround without applying the fix: configure Harbor to use non-DB authentication backend such as LDAP.CVE-2019-19023github.com/goharborharbor+2EPSS score1.62%
Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 has a Privilege Escalation Vulnerability in the VMware Harbor Container Registry for the Pivotal Platform.CVE-2019-19025github.com/goharborharbor+2EPSS score1.02%
Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows CSRF in the VMware Harbor Container Registry for the Pivotal Platform.CVE-2019-19030github.com/goharborharbor+1EPSS score1.91%
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.CVE-2019-19029github.com/goharborharbor+2EPSS score2.10%
Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via user-groups in the VMware Harbor Container Registry for the Pivotal Platform.