Page 3 of 13 results (0.006 seconds)

CVSS: 4.3EPSS: 0%CPEs: 7EXPL: 0

A User Enumeration flaw exists 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 about registered users can be obtained via the "search" functionality. Se presenta un fallo de Enumeración de Usuarios en Harbor. • https://github.com/goharbor/harbor/security/advisories/GHSA-6qj9-33j4-rvhg https://www.tenable.com/security/research/tra-2019-50 • CWE-269: Improper Privilege Management •

CVSS: 7.5EPSS: 0%CPEs: 5EXPL: 0

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. La API de Harbor tiene una vulnerabilidad de Control de Acceso Interrumpido. La vulnerabilidad permite a los administradores de proyectos utilizar la API de Harbor para crear una cuenta robot con permisos de acceso no autorizados para presionar y/o arrastrar en un proyecto al que no tienen acceso o control. • http://www.vmware.com/security/advisories/VMSA-2019-0016.html https://github.com/goharbor/harbor/security/advisories/GHSA-x2r2-w9c7-h624 https://landscape.cncf.io/selected=harbor • CWE-276: Incorrect Default Permissions •

CVSS: 6.5EPSS: 96%CPEs: 16EXPL: 4

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. core/api/user.go en Harbor versión 1.7.0 hasta la versión 1.8.2 permite a los usuarios que no son administradores crear cuentas de administrador mediante el POST /api/users API, cuando Harbor se configura con DB como back-end de autenticación y permite al usuario realizar el autorregistro. Esto se corrige en la versión 1.7.6, versión 1.8.3. versión 1.9.0. Solución alternativa sin aplicar la corrección: configure Harbor para que utilice el backend de autenticación que no sea de base de datos, como LDAP. • https://github.com/evilAdan0s/CVE-2019-16097 https://github.com/rockmelodies/CVE-2019-16097-batch https://github.com/ianxtianxt/CVE-2019-16097 https://github.com/luckybool1020/CVE-2019-16097 http://www.vmware.com/security/advisories/VMSA-2019-0015.html https://github.com/goharbor/harbor/commit/b6db8a8a106259ec9a2c48be8a380cb3b37cf517 https://github.com/goharbor/harbor/compare/v1.8.2...v1.9.0-rc1 https://github.com/goharbor/harbor/releases/tag/v1.7.6 https://github.com/goharbor/ha • CWE-862: Missing Authorization •