Filtered by vendor Zammad
Subscriptions
Filtered by product Zammad
Subscriptions
Total
72 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2020-14214 | 1 Zammad | 1 Zammad | 2024-08-04 | 6.5 Medium |
| Zammad before 3.3.1, when Domain Based Assignment is enabled, relies on a claimed e-mail address for authorization decisions. An attacker can register a new account that will have access to all tickets of an arbitrary Organization. | ||||
| CVE-2020-10096 | 1 Zammad | 1 Zammad | 2024-08-04 | 7.5 High |
| 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 attacker does not need to be authenticated with the application to view this information, as it would be available via the browser cache. | ||||
| CVE-2020-10098 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.4 Medium |
| 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-10101 | 1 Zammad | 1 Zammad | 2024-08-04 | 7.5 High |
| 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-10103 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.4 Medium |
| 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 active Zammad session. | ||||
| CVE-2020-10102 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.3 Medium |
| 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 as associated with a valid user. This behavior could be used as part of a two-stage automated attack. During the first stage, an attacker would iterate through a list of account names to determine which correspond to valid accounts. During the second stage, the attacker would use a list of common passwords to attempt to brute force credentials for accounts that were recognized by the system in the first stage. | ||||
| CVE-2020-10105 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.3 Medium |
| An issue was discovered in Zammad 3.0 through 3.2. It returns source code of static resources when submitting an OPTIONS request, rather than a GET request. Disclosure of source code allows for an attacker to formulate more precise attacks. Source code was disclosed for the file 404.html (/zammad/public/404.html) | ||||
| CVE-2020-10100 | 1 Zammad | 1 Zammad | 2024-08-04 | 6.5 Medium |
| 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 data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other companies. | ||||
| CVE-2020-10099 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.4 Medium |
| 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-10097 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.3 Medium |
| 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-10104 | 1 Zammad | 1 Zammad | 2024-08-04 | 4.3 Medium |
| 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-2021-44886 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.3 Medium |
| In Zammad 5.0.2, agents can configure "out of office" periods and substitute persons. If the substitute persons didn't have the same permissions as the original agent, they could receive ticket notifications for tickets that they have no access to. | ||||
| CVE-2021-43145 | 1 Zammad | 1 Zammad | 2024-08-04 | 8.1 High |
| With certain LDAP configurations, Zammad 5.0.1 was found to be vulnerable to unauthorized access with existing user accounts. | ||||
| CVE-2021-42137 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.3 Medium |
| An issue was discovered in Zammad before 5.0.1. In some cases, there is improper enforcement of the privilege requirement for viewing a list of tickets that shows title, state, etc. | ||||
| CVE-2021-42088 | 1 Zammad | 1 Zammad | 2024-08-04 | 6.1 Medium |
| An issue was discovered in Zammad before 4.1.1. The Chat functionality allows XSS because clipboard data is mishandled. | ||||
| CVE-2021-42091 | 1 Zammad | 1 Zammad | 2024-08-04 | 9.1 Critical |
| An issue was discovered in Zammad before 4.1.1. SSRF can occur via GitHub or GitLab integration. | ||||
| CVE-2021-42085 | 1 Zammad | 1 Zammad | 2024-08-04 | 5.4 Medium |
| An issue was discovered in Zammad before 4.1.1. There is stored XSS via a custom Avatar. | ||||
| CVE-2021-42087 | 1 Zammad | 1 Zammad | 2024-08-04 | 4.9 Medium |
| An issue was discovered in Zammad before 4.1.1. An admin can discover the application secret via the API. | ||||
| CVE-2021-42094 | 1 Zammad | 1 Zammad | 2024-08-04 | 9.8 Critical |
| An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages. | ||||
| CVE-2021-42090 | 1 Zammad | 1 Zammad | 2024-08-04 | 9.8 Critical |
| An issue was discovered in Zammad before 4.1.1. The Form functionality allows remote code execution because deserialization is mishandled. | ||||