CVE-2020-26032
https://notcve.org/view.php?id=CVE-2020-26032
28 Dec 2020 — An SSRF issue was discovered in Zammad before 3.4.1. The SMS configuration interface for Massenversand is implemented in a way that renders the result of a test request to the User. An attacker can use this to request any URL via a GET request from the network interface of the server. This may lead to disclosure of information from intranet systems. Se detectó un problema de SSRF en Zammad versiones anteriores a 3.4.1. • https://zammad.com/news/security-advisory-zaa-2020-15 • CWE-918: Server-Side Request Forgery (SSRF) •
CVE-2020-26033
https://notcve.org/view.php?id=CVE-2020-26033
28 Dec 2020 — An issue was discovered in Zammad before 3.4.1. The Tag and Link REST API endpoints (for add and delete) lack a CSRF token check. Se detectó un problema en Zammad versiones anteriores a 3.4.1. Los endpoints de la API REST de Etiqueta y Enlace (para agregar y eliminar) carecen de una comprobación de token CSRF • https://zammad.com/news/security-advisory-zaa-2020-17 • CWE-352: Cross-Site Request Forgery (CSRF) •
CVE-2020-26034
https://notcve.org/view.php?id=CVE-2020-26034
28 Dec 2020 — An account-enumeration issue was discovered in Zammad before 3.4.1. The Create User functionality is implemented in a way that would enable an anonymous user to guess valid user email addresses. The application responds differently depending on whether the input supplied was recognized as associated with a valid user. Se detectó un problema de enumeración de cuentas en Zammad versiones anteriores a 3.4.1. La funcionalidad Create User es implementada de una manera que permitiría a un usuario anónimo adi... • https://zammad.com/news/security-advisory-zaa-2020-14 •
CVE-2020-26035
https://notcve.org/view.php?id=CVE-2020-26035
28 Dec 2020 — An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket. Se detectó un problema en Zammad versiones anteriores a 3.4.1. Se presenta una vulnerabilidad de tipo XSS almacenado por medio de un elemento Tags en un Ticket • https://zammad.com/news/security-advisory-zaa-2020-21 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVE-2020-29158
https://notcve.org/view.php?id=CVE-2020-29158
28 Dec 2020 — An issue was discovered in Zammad before 3.5.1. An Agent with Customer permissions in a Group can bypass intended access control on internal Articles via the Ticket detail view. Se detectó un problema en Zammad versiones anteriores a 3.5.1. Un Agente con permisos de Cliente en un Grupo puede omitir un control de acceso previsto en los Artículos internos por medio de la vista de detalles del Ticket • https://github.com/zammad/zammad/commit/cf5a5e396058d4b134dd33d0a62b11c1733c98ab • CWE-862: Missing Authorization •
CVE-2020-29159
https://notcve.org/view.php?id=CVE-2020-29159
28 Dec 2020 — 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 •
CVE-2020-29160
https://notcve.org/view.php?id=CVE-2020-29160
28 Dec 2020 — 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 • CWE-862: Missing Authorization •
CVE-2020-14214
https://notcve.org/view.php?id=CVE-2020-14214
16 Jun 2020 — 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 d... • https://github.com/zammad/zammad/commit/40148392426f626cb779c76d6bdda0f67bd6069d • CWE-863: Incorrect Authorization •
CVE-2020-14213
https://notcve.org/view.php?id=CVE-2020-14213
16 Jun 2020 — 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 • CWE-862: Missing Authorization •
CVE-2020-10096
https://notcve.org/view.php?id=CVE-2020-10096
05 Mar 2020 — 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 •