1101 matches found
CVE-2020-29158
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-26031
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-26029
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...
Authentication flaw
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...
Cross site scripting
An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket...
Design/Logic Flaw
An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket. permission can access Tickets...
Input validation
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...
Server side request forgery (ssrf)
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 le...
Design/Logic Flaw
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...
Cross site request forgery (csrf)
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...
Design/Logic Flaw
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...
Design/Logic Flaw
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...
Spoofing
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...
Authorization
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-26028
Zammad prior to 3.4.1 contains an improper access control vulnerability where Admin Users lacking the ticket.* permission can access Tickets. The issue, described across multiple sources (NVD entry for CVE-2020-26028 and Red Hat/CNVD entries), stems from insufficient permission checks in the admi...
CVE-2020-26028
An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket. permission can access Tickets...
CVE-2020-26029
CVE-2020-26029 affects Zammad before 3.4.1, with incorrect authorization checks for impersonation requests via the X-On-Behalf-Of header. The checks are applied to the actual user rather than the user in the X-On-Behalf-Of header, creating a potential authorization bypass. The CVSS data indicates...
CVE-2020-26029
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
CVE-2020-26030 affects Zammad prior to 3.4.1. There is an authentication bypass in the SSO endpoint via a crafted header when SSO is not configured, allowing an attacker to create a valid authenticated session and perform actions in the name of other users. The description is corroborated across ...
CVE-2020-26030
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...