CVEdetails.com the ultimate security vulnerability data source
(e.g.: CVE-2009-1234 or 2010-1234 or 20101234)
Log In   Register
  What's the CVSS score of your company?
Vulnerability Feeds & WidgetsNew   www.itsecdb.com  

Zammad » Zammad » * * * * : Security Vulnerabilities

Cpe Name:cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*
Press ESC to close
# CVE ID CWE ID # of Exploits Vulnerability Type(s) Publish Date Update Date Score Gained Access Level Access Complexity Authentication Conf. Integ. Avail.
1 CVE-2021-42137 269 2021-10-11 2021-10-19
5.0
None Remote Low Not required Partial None None
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.
2 CVE-2021-42094 77 2021-10-07 2021-10-14
7.5
None Remote Low Not required Partial Partial Partial
An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages.
3 CVE-2021-42093 Exec Code 2021-10-07 2021-10-14
6.5
None Remote Low ??? Partial Partial Partial
An issue was discovered in Zammad before 4.1.1. An admin can execute code on the server via a crafted request that manipulates triggers.
4 CVE-2021-42092 79 XSS 2021-10-07 2021-10-14
3.5
None Remote Medium ??? None Partial None
An issue was discovered in Zammad before 4.1.1. Stored XSS may occur via an Article during addition of an attachment to a Ticket.
5 CVE-2021-42091 918 2021-10-07 2021-10-14
6.4
None Remote Low Not required Partial Partial None
An issue was discovered in Zammad before 4.1.1. SSRF can occur via GitHub or GitLab integration.
6 CVE-2021-42090 502 Exec Code 2021-10-07 2021-10-14
7.5
None Remote Low Not required Partial Partial Partial
An issue was discovered in Zammad before 4.1.1. The Form functionality allows remote code execution because deserialization is mishandled.
7 CVE-2021-42089 200 +Info 2021-10-07 2021-10-14
5.0
None Remote Low Not required Partial None None
An issue was discovered in Zammad before 4.1.1. The REST API discloses sensitive information.
8 CVE-2021-42088 79 XSS 2021-10-07 2021-10-13
4.3
None Remote Medium Not required None Partial None
An issue was discovered in Zammad before 4.1.1. The Chat functionality allows XSS because clipboard data is mishandled.
9 CVE-2021-42087 668 2021-10-07 2021-10-14
4.0
None Remote Low ??? Partial None None
An issue was discovered in Zammad before 4.1.1. An admin can discover the application secret via the API.
10 CVE-2021-42086 269 2021-10-07 2021-10-14
6.5
None Remote Low ??? Partial Partial Partial
An issue was discovered in Zammad before 4.1.1. An Agent account can modify account data, and gain admin access, via a crafted request.
11 CVE-2021-42085 79 XSS 2021-10-07 2021-10-13
3.5
None Remote Medium ??? None Partial None
An issue was discovered in Zammad before 4.1.1. There is stored XSS via a custom Avatar.
12 CVE-2021-42084 835 DoS 2021-10-07 2021-10-14
4.0
None Remote Low ??? None None Partial
An issue was discovered in Zammad before 4.1.1. An attacker with valid agent credentials may send a series of crafted requests that cause an endless loop and thus cause denial of service.
13 CVE-2021-35303 79 XSS 2021-06-28 2021-07-02
4.3
None Remote Medium Not required None Partial None
Cross Site Scripting (XSS) in Zammad 1.0.x up to 4.0.0 allows remote attackers to execute arbitrary web script or HTML via the User Avatar attribute.
14 CVE-2021-35302 668 +Info 2021-06-28 2021-07-02
5.0
None Remote Low Not required Partial None None
Incorrect Access Control for linked Tickets in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information.
15 CVE-2021-35301 668 +Info 2021-06-28 2021-07-02
5.0
None Remote Low Not required Partial None None
Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information via the Ticket Article detail view.
16 CVE-2021-35300 1021 2021-06-28 2021-07-02
4.3
None Remote Medium Not required None Partial None
Text injection/Content Spoofing in 404 page in Zammad 1.0.x up to 4.0.0 could allow remote attackers to manipulate users into visiting the attackers' page.
17 CVE-2021-35299 668 +Info 2021-06-28 2021-07-01
5.0
None Remote Low Not required Partial None None
Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows attackers to obtain sensitive information via email connection configuration probing.
18 CVE-2021-35298 79 XSS 2021-06-28 2021-07-01
4.3
None Remote Medium Not required None Partial None
Cross Site Scripting (XSS) in Zammad 1.0.x up to 4.0.0 allows remote attackers to execute arbitrary web script or HTML via multiple models that contain a 'note' field to store additional information.
19 CVE-2020-29160 863 2020-12-28 2021-07-21
5.0
None Remote Low Not required None Partial None
An issue was discovered in Zammad before 3.5.1. A REST API call allows an attacker to change Ticket Article data in a way that defeats auditing.
20 CVE-2020-29159 2020-12-28 2020-12-29
4.0
None Remote Low ??? Partial None None
An issue was discovered in Zammad before 3.5.1. The default signup Role (for newly created Users) can be a privileged Role, if configured by an admin. This behvaior was unintended.
21 CVE-2020-29158 863 Bypass 2020-12-28 2021-07-21
4.0
None Remote Low ??? Partial None None
An issue was discovered in Zammad before 3.5.1. An Agent with Customer permissions in a Group can bypass intended access control on internal Articles via the Ticket detail view.
22 CVE-2020-26035 79 XSS 2020-12-28 2020-12-29
3.5
None Remote Medium ??? None Partial None
An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket.
23 CVE-2020-26034 2020-12-28 2020-12-30
4.0
None Remote Low ??? Partial None None
An account-enumeration issue was discovered in Zammad before 3.4.1. The Create User functionality is implemented in a way that would enable an anonymous user to guess valid user email addresses. The application responds differently depending on whether the input supplied was recognized as associated with a valid user.
24 CVE-2020-26033 352 CSRF 2020-12-28 2020-12-29
5.8
None Remote Medium Not required Partial Partial None
An issue was discovered in Zammad before 3.4.1. The Tag and Link REST API endpoints (for add and delete) lack a CSRF token check.
25 CVE-2020-26032 918 2020-12-28 2020-12-29
5.0
None Remote Low Not required Partial None None
An SSRF issue was discovered in Zammad before 3.4.1. The SMS configuration interface for Massenversand is implemented in a way that renders the result of a test request to the User. An attacker can use this to request any URL via a GET request from the network interface of the server. This may lead to disclosure of information from intranet systems.
26 CVE-2020-26031 276 2020-12-28 2020-12-29
4.0
None Remote Low ??? Partial None None
An issue was discovered in Zammad before 3.4.1. The global-search feature leaks Knowledge Base drafts to Knowledge Base readers (who are authenticated but have insufficient permissions).
27 CVE-2020-26030 287 Bypass 2020-12-28 2020-12-29
7.5
None Remote Low Not required Partial Partial Partial
An issue was discovered in Zammad before 3.4.1. There is an authentication bypass in the SSO endpoint via a crafted header, when SSO is not configured. An attacker can create a valid and authenticated session that can be used to perform any actions in the name of other users.
28 CVE-2020-26029 863 2020-12-28 2020-12-29
4.0
None Remote Low ??? Partial None None
An issue was discovered in Zammad before 3.4.1. There are wrong authorization checks for impersonation requests via X-On-Behalf-Of. The authorization checks are performed for the actual user and not the one given in the X-On-Behalf-Of header.
29 CVE-2020-26028 863 2020-12-28 2020-12-29
4.0
None Remote Low ??? Partial None None
An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket.* permission can access Tickets.
30 CVE-2020-14214 862 2020-06-16 2021-07-21
5.8
None Remote Medium Not required Partial Partial None
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.
31 CVE-2020-14213 862 2020-06-16 2020-06-23
5.5
None Remote Low ??? Partial Partial None
In Zammad before 3.3.1, a Customer has ticket access that should only be available to an Agent (e.g., read internal data, split, or merge).
32 CVE-2020-10105 200 +Info 2020-03-05 2021-07-21
5.0
None Remote Low Not required Partial None None
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)
33 CVE-2020-10104 200 +Info 2020-03-05 2020-03-05
4.0
None Remote Low ??? Partial None None
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.
34 CVE-2020-10103 79 Exec Code XSS 2020-03-05 2020-03-05
3.5
None Remote Medium ??? None Partial None
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.
35 CVE-2020-10102 203 2020-03-05 2020-03-05
3.5
None Remote Medium ??? Partial None None
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.
36 CVE-2020-10101 20 2020-03-05 2021-07-21
5.0
None Remote Low Not required None None Partial
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.
37 CVE-2020-10100 200 +Info 2020-03-05 2021-07-21
4.0
None Remote Low ??? Partial None None
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.
38 CVE-2020-10099 79 Exec Code XSS 2020-03-05 2020-03-05
3.5
None Remote Medium ??? None Partial None
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.
39 CVE-2020-10098 79 Exec Code XSS 2020-03-05 2020-03-05
3.5
None Remote Medium ??? None Partial None
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.
40 CVE-2020-10097 209 2020-03-05 2020-03-05
5.0
None Remote Low Not required Partial None None
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.
41 CVE-2020-10096 200 +Info 2020-03-05 2020-03-05
5.0
None Remote Low Not required Partial None None
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.
42 CVE-2019-1010018 79 Exec Code XSS 2019-07-16 2019-10-09
4.3
None Remote Medium Not required None Partial None
Zammad GmbH Zammad 2.3.0 and earlier is affected by: Cross Site Scripting (XSS) - CWE-80. The impact is: Execute java script code on users browser. The component is: web app. The attack vector is: the victim must open a ticket. The fixed version is: 2.3.1, 2.2.2 and 2.1.3.
43 CVE-2018-1000154 79 Exec Code XSS 2018-04-05 2018-05-10
4.3
None Remote Medium Not required None Partial None
Zammad GmbH Zammad version 2.3.0 and earlier contains a Improper Neutralization of Script-Related HTML Tags in a Web Page (CWE-80) vulnerability in the subject of emails which are not html quoted in certain cases. This can result in the embedding and execution of java script code on users browser. This attack appear to be exploitable via the victim openning a ticket. This vulnerability appears to have been fixed in 2.3.1, 2.2.2 and 2.1.3.
44 CVE-2017-6081 352 CSRF 2017-03-13 2019-03-14
6.8
None Remote Medium Not required Partial Partial Partial
A CSRF issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie.
45 CVE-2017-6080 352 2017-03-13 2019-10-03
7.5
None Remote Low Not required Partial Partial Partial
An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1, caused by lack of a protection mechanism involving HTTP Access-Control headers. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie and receive the result.
46 CVE-2017-5621 79 XSS 2017-03-13 2017-03-18
4.3
None Remote Medium Not required None Partial None
An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. XSS can be triggered via malicious HTML in a chat message or the content of a ticket article, when using either the REST API or the WebSocket API.
47 CVE-2017-5620 79 XSS 2017-03-13 2017-03-18
4.3
None Remote Medium Not required None Partial None
An XSS issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. Attachments are opened in a new tab instead of getting downloaded. This creates an attack vector of executing code in the domain of the application.
48 CVE-2017-5619 287 2017-03-13 2019-10-03
7.5
None Remote Low Not required Partial Partial Partial
An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. Attackers can login with the hashed password itself (e.g., from the DB) instead of the valid password string.
Total number of vulnerabilities : 48   Page : 1 (This Page)
CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site. OVAL is a registered trademark of The MITRE Corporation and the authoritative source of OVAL content is MITRE's OVAL web site.
Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.