6 results (0.016 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 •