Information disclosure

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

Cross site scripting

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

Authentication flaw

An issue was discovered in Zammad 3.0 through 3.2. After authentication, it transmits sensitive information to the user that may be compromised and used by an attacker to gain unauthorized access. Hashed passwords are returned to the user when visiting a certain URL...

CVE-2020-10096

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

CVE-2020-10096

CVE-2020-10096 affects Zammad 3.0–3.2 and involves a failure to prevent caching of confidential data in browser memory. An attacker who remotely compromises or physically gains access to a user’s workstation can read sensitive information from the browser cache without authenticating to the appli...

CVE-2020-10097

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

CVE-2020-10097

The CVE-2020-10097 issue affects Zammad 3.0–3.2. Multiple sources (NVD, Red Hat, OSV, CVE lists) report that the application may respond with verbose error messages that disclose internal application or infrastructure information. This information could aid attackers in exploiting other vulnerabi...

CVE-2020-10098

CVE-2020-10098 affects Zammad 3.0–3.2 via an XSS in the Email functionality. A low-privilege user can supply malicious code in an email, which will execute in the browser of any user who opens the Ticket containing the Article created from that Email. Exploitation details and remediation/fix are ...

CVE-2020-10098

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

CVE-2020-10099

CVE-2020-10099 affects Zammad 3.0–3.2 where a stored/reflected XSS can be introduced by a low-privileged user via the Ticket functionality. The malicious JavaScript executes in the browser of any user who opens the affected ticket or has the ticket in the Toolbar. No remediation details are provi...

CVE-2020-10099

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

CVE-2020-10100

CVE-2020-10100 (Zammad) affects Zammad 3.0–3.2 and arises from improper access controls in the ticket/customer data view, enabling users from one company to access ticket data from other companies in a multi-tenant deployment. The impact is limited to confidentiality (high impact per CVE sources)...

CVE-2020-10100

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

CVE-2020-10101

CVE-2020-10101 affects Zammad 3.0–3.2 where the WebSocket server crashes when non‑JSON messages are sent. The root cause is inadequate validation of message format and unhandled parsing errors, causing a service process crash. Public details in the connected sources reiterate the same description...

CVE-2020-10101

An issue was discovered in Zammad 3.0 through 3.2. The WebSocket server crashes when messages in non-JSON format are sent by an attacker. The message format is not properly checked and parsing errors not handled. This leads to a crash of the service process...

CVE-2020-10102

An issue was discovered in Zammad 3.0 through 3.2. The Forgot Password functionality is implemented in a way that would enable an anonymous user to guess valid user emails. In the current implementation, the application responds differently depending on whether the input supplied was recognized a...

CVE-2020-10102

Technical details about CVE-2020-10102 are not provided in the connected documents. Monitor for updates from vendors and security advisories.

CVE-2020-10103

An XSS issue was discovered in Zammad 3.0 through 3.2. Malicious code can be provided by a low-privileged user through the File Upload functionality in Zammad. The malicious JavaScript will execute within the browser of any user who opens a specially crafted link to the uploaded file with an acti...

CVE-2020-10103

The CVE-2020-10103 issue affects Zammad versions 3.0 through 3.2 and is an XSS vulnerability exploitable via the File Upload feature. A low-privileged user can supply malicious JavaScript in an uploaded file, which will execute in the browsers of users with an active Zammad session when they clic...

CVE-2020-10104

An issue was discovered in Zammad 3.0 through 3.2. After authentication, it transmits sensitive information to the user that may be compromised and used by an attacker to gain unauthorized access. Hashed passwords are returned to the user when visiting a certain URL...