CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 4.9EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-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 •
CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0CVE-2020-10097
https://notcve.org/view.php?id=CVE-2020-10097
05 Mar 2020 — An issue was discovered in Zammad 3.0 through 3.2. It may respond with verbose error messages that disclose internal application or infrastructure information. This information could aid attackers in successfully exploiting other vulnerabilities. Se detectó un problema en Zammad versiones 3.0 hasta 3.2. Puede responder con mensajes de error detallados que revelan información interna de la aplicación o la infraestructura. • https://zammad.com/news/security-advisory-zaa-2020-10 • CWE-209: Generation of Error Message Containing Sensitive Information •
CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 0CVE-2020-10098
https://notcve.org/view.php?id=CVE-2020-10098
05 Mar 2020 — An XSS issue was discovered in Zammad 3.0 through 3.2. Malicious code can be provided by a low-privileged user through the Email functionality. The malicious JavaScript will execute within the browser of any user who opens the Ticket with the Article created from that Email. Se detectó un problema de tipo XSS en Zammad versiones 3.0 hasta 3.2. Un usuario poco privilegiado puede proporcionar código malicioso por medio de la funcionalidad Email. • https://zammad.com/news/security-advisory-zaa-2020-03 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 0CVE-2020-10099
https://notcve.org/view.php?id=CVE-2020-10099
05 Mar 2020 — An XSS issue was discovered in Zammad 3.0 through 3.2. Malicious code can be provided by a low-privileged user through the Ticket functionality in Zammad. The malicious JavaScript will execute within the browser of any user who opens the ticket or has the ticket within the Toolbar. Se detectó un problema de tipo XSS en Zammad versiones 3.0 hasta 3.2. Un usuario poco privilegiado puede proporcionar código malicioso por medio de la funcionalidad Ticket en Zammad. • https://zammad.com/news/security-advisory-zaa-2020-01 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-10100
https://notcve.org/view.php?id=CVE-2020-10100
05 Mar 2020 — An issue was discovered in Zammad 3.0 through 3.2. It allows for users to view ticket customer details associated with specific customers. However, the application does not properly implement access controls related to this functionality. As such, users of one company are able to access ticket data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other c... • https://zammad.com/news/security-advisory-zaa-2020-05 •