66 results (0.007 seconds)

CVSS: 6.5EPSS: 0%CPEs: 1EXPL: 0

18 May 2023 — An issue in Zammad v5.4.0 allows attackers to bypass e-mail verification using an arbitrary address and manipulate the data of the generated user. Attackers are also able to gain unauthorized access to existing tickets. • https://zammad.com/de/advisories/zaa-2023-03 • CWE-863: Incorrect Authorization •

CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0

02 May 2023 — Zammad 5.3.x (Fixed 5.4.0) is vulnerable to Incorrect Access Control. An authenticated attacker could gain information about linked accounts of users involved in their tickets using the Zammad API. • https://zammad.com/en/advisories/zaa-2023-02 •

CVSS: 6.8EPSS: 0%CPEs: 1EXPL: 0

02 May 2023 — Zammad 5.3.x (Fixed in 5.4.0) is vulnerable to Incorrect Access Control. An authenticated attacker with agent and customer roles could perform unauthorized changes on articles where they only have customer permissions. • https://zammad.com/en/advisories/zaa-2023-01 •

CVSS: 10.0EPSS: 0%CPEs: 1EXPL: 0

03 Feb 2023 — A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server. • https://zammad.com/de/advisories/zaa-2022-11 •

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

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: 0

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: 0

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: 0

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: 0

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: 0

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 •