CVE-2022-48021: Undefined Security Weakness

A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server...

CVE-2022-48023: Undefined Security Weakness

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...

PT-2023-15553

Name of the Vulnerable Software and Affected Versions Zammad version 5.3.0 Description An issue in the component "/api/v1/mentions" allows authenticated attackers with agent permissions to view information about tickets they are not authorized to see. Recommendations For Zammad version 5.3.0,...

CVE-2022-48022

CVE-2022-48022 describes an access control flaw in Zammad v5.3.0 where the component at /api/v1/mentions allows authenticated users with agent permissions to view information about tickets they should not be allowed to see. The issue is confirmed across multiple sources in the connected set (NVD,...

CVE-2022-48021

A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server...

CVE-2022-48023

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...

PT-2023-15552

Name of the Vulnerable Software and Affected Versions Zammad version 5.3.0 Description A vulnerability allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server. Recommendations For Zammad version 5.3.0, at the moment, there is no information about...

CVE-2022-48023

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...

Zammad Access Control Error Vulnerability (CNVD-2022-66765)

Zammad is a suite of ticket management software from the German company Zammad. An access control error vulnerability exists in Zammad version 5.2.1. The vulnerability stems from faulty access control in the program, where Zammad's asset handling mechanism has logic that ensures that client users...

CVE-2022-40817

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...

CVE-2022-40816

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...

Improper access control

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...

Design/Logic Flaw

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...

CVE-2022-40816

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...

CVE-2022-40816

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...

CVE-2022-40816

Zammad 5.2.1 is affected by an Incorrect Access Control flaw where the asset handling logic fails over WebSocket connections, allowing an authenticated attacker to query the Zammad API and fetch other users’ personal data. The issue manifests when access control checks are bypassed through the we...

CVE-2022-40816

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...

CVE-2022-40816

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...

CVE-2022-40817

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...

CVE-2022-40817

CVE-2022-40817 affects Zammad 5.2.1 where a fine-grained permission model intended for read-only tickets still allowed certain operations (adding/removing links, tags, related answers). Root cause: permissions logic did not enforce read-only restrictions for these actions. Impact: unauthorized-li...