CVSS: 4.9EPSS: 0%CPEs: 1EXPL: 0CVE-2020-29159
https://notcve.org/view.php?id=CVE-2020-29159
An issue was discovered in Zammad before 3.5.1. The default signup Role (for newly created Users) can be a privileged Role, if configured by an admin. This behvaior was unintended. Se detectó un problema en Zammad versiones anteriores a 3.5.1. El Rol de registro predeterminado (para Usuarios recién creados) puede ser un rol privilegiado, si es configurado por un administrador. • https://github.com/zammad/zammad/commit/f0462d4c20c2968b52b5dc6a585f26c0409b4fc4 https://zammad.com/en/advisories/zaa-2020-22 •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-29160
https://notcve.org/view.php?id=CVE-2020-29160
An issue was discovered in Zammad before 3.5.1. A REST API call allows an attacker to change Ticket Article data in a way that defeats auditing. Se detectó un problema en Zammad versiones anteriores a 3.5.1. Una llamada a la API REST permite a un atacante cambiar los datos de Ticket Article en una manera que anula la auditoría • https://github.com/zammad/zammad/commit/28944de180a88698509a656f61558bf9d7f810f4 https://zammad.com/en/advisories/zaa-2020-24 • CWE-862: Missing Authorization •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-14214
https://notcve.org/view.php?id=CVE-2020-14214
Zammad before 3.3.1, when Domain Based Assignment is enabled, relies on a claimed e-mail address for authorization decisions. An attacker can register a new account that will have access to all tickets of an arbitrary Organization. En Zammad en versiones anteriores a la 3.3.1, cuando se habilita la asignación basada en el dominio, se basa en una dirección de correo electrónico reclamada para las decisiones de autorización. Un atacante puede registrar una nueva cuenta que tendrá acceso a todas las entradas de una Organización arbitraria • https://github.com/zammad/zammad/commit/40148392426f626cb779c76d6bdda0f67bd6069d https://zammad.com/news/security-advisory-zaa-2020-12 • CWE-863: Incorrect Authorization •
CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-14213
https://notcve.org/view.php?id=CVE-2020-14213
In Zammad before 3.3.1, a Customer has ticket access that should only be available to an Agent (e.g., read internal data, split, or merge). En Zammad en versiones anteriores a la 3.3.1, un Cliente tiene un acceso de entrada que sólo debería estar disponible para un Agente (por ejemplo, leer datos internos, dividir o fusionar) • https://github.com/zammad/zammad/commit/6e56aee25439b7a3211a6704a9d60453ad623ae4 https://zammad.com/news/security-advisory-zaa-2020-13 • CWE-862: Missing Authorization •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-10096
https://notcve.org/view.php?id=CVE-2020-10096
An issue was discovered in Zammad 3.0 through 3.2. It does not prevent caching of confidential data within browser memory. An attacker who either remotely compromises or obtains physical access to a user's workstation can browse the browser cache contents and obtain sensitive information. The attacker does not need to be authenticated with the application to view this information, as it would be available via the browser cache. Se detectó un problema en Zammad versiones 3.0 hasta 3.2. • https://zammad.com/news/security-advisory-zaa-2020-11 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •