Zammad
by Zammad
Source repositories
CVEs (90)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2021-35298 | 0.00 | — | 0.01 | Jun 28, 2021 | 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. | |||
| CVE-2021-35299 | 0.00 | — | 0.01 | Jun 28, 2021 | Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows attackers to obtain sensitive information via email connection configuration probing. | |||
| CVE-2021-35300 | 0.00 | — | 0.01 | Jun 28, 2021 | 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. | |||
| CVE-2021-35301 | 0.00 | — | 0.01 | Jun 28, 2021 | 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. | |||
| CVE-2021-35302 | 0.00 | — | 0.01 | Jun 28, 2021 | Incorrect Access Control for linked Tickets in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information. | |||
| CVE-2021-35303 | 0.00 | — | 0.01 | Jun 28, 2021 | 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. | |||
| CVE-2020-26028 | 0.00 | — | 0.01 | Dec 28, 2020 | An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket.* permission can access Tickets. | |||
| CVE-2020-26029 | 0.00 | — | 0.01 | Dec 28, 2020 | 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. | |||
| CVE-2020-26030 | 0.00 | — | 0.01 | Dec 28, 2020 | 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. | |||
| CVE-2020-26031 | 0.00 | — | 0.01 | Dec 28, 2020 | 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). | |||
| CVE-2020-26032 | 0.00 | — | 0.01 | Dec 28, 2020 | 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… | |||
| CVE-2020-26033 | 0.00 | — | 0.00 | Dec 28, 2020 | 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. | |||
| CVE-2020-26034 | 0.00 | — | 0.01 | Dec 28, 2020 | 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… | |||
| CVE-2020-26035 | 0.00 | — | 0.01 | Dec 28, 2020 | An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket. | |||
| CVE-2020-29158 | 0.00 | — | 0.01 | Dec 28, 2020 | 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. | |||
| CVE-2020-29159 | 0.00 | — | 0.01 | Dec 28, 2020 | 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. | |||
| CVE-2020-29160 | 0.00 | — | 0.01 | Dec 28, 2020 | 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. | |||
| CVE-2020-14214 | 0.00 | — | 0.01 | Jun 16, 2020 | 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-14213 | 0.00 | — | 0.01 | Jun 16, 2020 | 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). | |||
| CVE-2020-10096 | 0.00 | — | 0.01 | Mar 5, 2020 | 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… |
- CVE-2021-35298Jun 28, 2021risk 0.00cvss —epss 0.01
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.
- CVE-2021-35299Jun 28, 2021risk 0.00cvss —epss 0.01
Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows attackers to obtain sensitive information via email connection configuration probing.
- CVE-2021-35300Jun 28, 2021risk 0.00cvss —epss 0.01
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.
- CVE-2021-35301Jun 28, 2021risk 0.00cvss —epss 0.01
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.
- CVE-2021-35302Jun 28, 2021risk 0.00cvss —epss 0.01
Incorrect Access Control for linked Tickets in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information.
- CVE-2021-35303Jun 28, 2021risk 0.00cvss —epss 0.01
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.
- CVE-2020-26028Dec 28, 2020risk 0.00cvss —epss 0.01
An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket.* permission can access Tickets.
- CVE-2020-26029Dec 28, 2020risk 0.00cvss —epss 0.01
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.
- CVE-2020-26030Dec 28, 2020risk 0.00cvss —epss 0.01
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.
- CVE-2020-26031Dec 28, 2020risk 0.00cvss —epss 0.01
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).
- CVE-2020-26032Dec 28, 2020risk 0.00cvss —epss 0.01
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…
- CVE-2020-26033Dec 28, 2020risk 0.00cvss —epss 0.00
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.
- CVE-2020-26034Dec 28, 2020risk 0.00cvss —epss 0.01
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…
- CVE-2020-26035Dec 28, 2020risk 0.00cvss —epss 0.01
An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket.
- CVE-2020-29158Dec 28, 2020risk 0.00cvss —epss 0.01
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.
- CVE-2020-29159Dec 28, 2020risk 0.00cvss —epss 0.01
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.
- CVE-2020-29160Dec 28, 2020risk 0.00cvss —epss 0.01
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.
- CVE-2020-14214Jun 16, 2020risk 0.00cvss —epss 0.01
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-14213Jun 16, 2020risk 0.00cvss —epss 0.01
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).
- CVE-2020-10096Mar 5, 2020risk 0.00cvss —epss 0.01
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…
Page 4 of 5