CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2022-48022
https://notcve.org/view.php?id=CVE-2022-48022
03 Feb 2023 — An issue in the component /api/v1/mentions of Zammad v5.3.0 allows authenticated attackers with agent permissions to view information about tickets they are not authorized to see. • https://zammad.com/de/advisories/zaa-2022-13 •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2022-48023
https://notcve.org/view.php?id=CVE-2022-48023
03 Feb 2023 — Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker to perform changes on the tags of their customer tickets using the Zammad API. This is now corrected in v5.3.1 so that only agents with write permissions may change ticket tags. • https://zammad.com/de/advisories/zaa-2022-12 •
CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0CVE-2022-40816
https://notcve.org/view.php?id=CVE-2022-40816
27 Sep 2022 — Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to see personal information of other users. This logic was not effective when used through a web socket connection, so that a logged-in attacker would be able to fetch personal data of other users by querying the Zammad API. This issue is fixed in , 5.2.2. Zammad versión 5.2.1, es vulnerable a un Control de Acceso Incorrecto. • https://zammad.com/de/advisories/zaa-2022-09 • CWE-863: Incorrect Authorization •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2022-40817
https://notcve.org/view.php?id=CVE-2022-40817
27 Sep 2022 — Zammad 5.2.1 has a fine-grained permission model that allows to configure read-only access to tickets. However, agents were still wrongly able to perform some operations on such tickets, like adding and removing links, tags. and related answers. This issue has been fixed in 5.2.2. Zammad versión 5.2.1, presenta un modelo de permisos de grano fino que permite configurar el acceso de sólo lectura a los tickets. Sin embargo, los agentes todavía podían llevar a cabo erróneamente algunas operaciones en dichos ti... • https://zammad.com/de/advisories/zaa-2022-10 • CWE-732: Incorrect Permission Assignment for Critical Resource •
CVSS: 10.0EPSS: 0%CPEs: 2EXPL: 0CVE-2022-35490
https://notcve.org/view.php?id=CVE-2022-35490
08 Aug 2022 — Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess login credentials. After a configurable amount of attempts, users are invalidated and logins prevented. An attacker might work around this prevention, enabling them to send more than the configured amount of requests before the user invalidation takes place. Zammad 5.2.0 es vulnerable a la escalada de privilegios. • https://zammad.com/de/advisories/zaa-2022-07 • CWE-307: Improper Restriction of Excessive Authentication Attempts •
CVSS: 6.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-35489
https://notcve.org/view.php?id=CVE-2022-35489
08 Aug 2022 — In Zammad 5.2.0, customers who have secondary organizations assigned were able to see all organizations of the system rather than only those to which they are assigned. En Zammad versión 5.2.0, los clientes que presentan asignadas organizaciones secundarias podían visualizar todas las organizaciones del sistema en lugar de sólo aquellas a las que están asignadas • https://zammad.com/de/advisories/zaa-2022-06 •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-35488
https://notcve.org/view.php?id=CVE-2022-35488
08 Aug 2022 — In Zammad 5.2.0, an attacker could manipulate the rate limiting in the 'forgot password' feature of Zammad, and thereby send many requests for a known account to cause Denial Of Service by many generated emails which would also spam the victim. En Zammad versión 5.2.0, un atacante podía manipular la limitación de la tasa en la funcionalidad "forgot password" de Zammad, y así enviar muchas peticiones a una cuenta conocida para causar una Denegación de Servicio por medio de muchos correos electrónicos generad... • https://zammad.com/de/advisories/zaa-2022-05 •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-35487
https://notcve.org/view.php?id=CVE-2022-35487
08 Aug 2022 — Zammad 5.2.0 suffers from Incorrect Access Control. Zammad did not correctly perform authorization on certain attachment endpoints. This could be abused by an unauthenticated attacker to gain access to attachments, such as emails or attached files. Zammad versión 5.2.0, sufre un Control de Acceso Incorrecto. Zammad no llevaba a cabo correctamente la autorización en determinados extremos de los archivos adjuntos. • https://zammad.com/de/advisories/zaa-2022-08 • CWE-863: Incorrect Authorization •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-29700
https://notcve.org/view.php?id=CVE-2022-29700
27 Apr 2022 — A lack of password length restriction in Zammad v5.1.0 allows for the creation of extremely long passwords which can cause a Denial of Service (DoS) during password verification. Una falta de restricción de la longitud de las contraseñas en Zammad versión v5.1.0, permite la creación de contraseñas extremadamente largas que pueden causar una Denegación de Servicio (DoS) durante la verificación de la contraseña • https://zammad.com/en/advisories/zaa-2022-03 • CWE-521: Weak Password Requirements •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-29701
https://notcve.org/view.php?id=CVE-2022-29701
27 Apr 2022 — A lack of rate limiting in the 'forgot password' feature of Zammad v5.1.0 allows attackers to send an excessive amount of reset requests for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages. Una falta de limitación de la tasa en la funcionalidad "forgot password" de Zammad versión v5.1.0, permite a atacantes enviar una cantidad excesiva de peticiones de restablecimiento para un usuario legítimo, conllevando a una posible Denegación de Servicio ... • https://zammad.com/en/advisories/zaa-2022-04 • CWE-770: Allocation of Resources Without Limits or Throttling •