Rezultati pretraživanja za 'Proizvođač: zammad'
| ID | CVSS | Sažetak | Zadnje ažurirano | Objavljeno |
|---|---|---|---|---|
| CVE-2023-50455 | 7.5 | An issue was discovered in Zammad before 6.2.0. Due to lack of rate limiting in the "email address verification" feature, an attacker could send many requests for a known address to cause Denial Of Service (generation of many emails, which would also | 2023-12-13 18:03:08 | 2023-12-10 19:15:07 |
| CVE-2023-50457 | 4.3 | An issue was discovered in Zammad before 6.2.0. When listing tickets linked to a knowledge base answer, or knowledge base answers of a ticket, a user could see entries for which they lack permissions. | 2023-12-13 18:02:33 | 2023-12-10 19:15:07 |
| CVE-2023-50453 | 5.3 | An issue was discovered in Zammad before 6.2.0. It uses the public endpoint /api/v1/signshow for its login screen. This endpoint returns internal configuration data of user object attributes, such as selectable values, which should not be visible to | 2023-12-13 15:58:08 | 2023-12-10 19:15:07 |
| CVE-2022-35489 | 6.5 | In Zammad 5.2.0, customers who have secondary organizations assigned were able to see all organizations of the system rather than only those to which they are assigned. | 2023-08-08 14:22:00 | 2022-08-08 14:15:00 |
| CVE-2022-35488 | 7.5 | In Zammad 5.2.0, an attacker could manipulate the rate limiting in the 'forgot password' feature of Zammad, and thereby send many requests for a known account to cause Denial Of Service by many generated emails which would also spam the victim. | 2023-08-08 14:22:00 | 2022-08-08 14:15:00 |
| CVE-2022-27332 | 5.8 | An access control issue in Zammad v5.0.3 allows attackers to write entries to the CTI caller log without authentication. This vulnerability can allow attackers to execute phishing attacks or cause a Denial of Service (DoS). | 2023-08-08 14:22:00 | 2022-04-27 03:15:00 |
| CVE-2021-44886 | 5.0 | 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. | 2023-08-08 14:22:00 | 2022-02-04 15:15:00 |
| CVE-2022-48023 | 4.3 | Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker to perform changes on the tags of their customer tickets using the Zammad API. This is now corrected in v5.3.1 so that only agents with write permissions may change | 2023-02-09 17:49:00 | 2023-02-03 01:15:00 |
| CVE-2022-35490 | 9.8 | Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess login credentials. After a configurable amount of attempts, users are invalidated and logins prevented. An attacker might work aro | 2022-08-12 14:49:00 | 2022-08-08 14:15:00 |
| CVE-2022-35487 | 7.5 | Zammad 5.2.0 suffers from Incorrect Access Control. Zammad did not correctly perform authorization on certain attachment endpoints. This could be abused by an unauthenticated attacker to gain access to attachments, such as emails or attached files. | 2022-08-12 14:37:00 | 2022-08-08 14:15:00 |
| ID | CVSS | Sažetak | Zadnje ažurirano | Objavljeno |
|---|
Stranica
/10
Zapisa po stranici: