Page 9 of 50 results (0.002 seconds)

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0

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. • https://zammad.com/news/security-advisory-zaa-2020-07 • CWE-203: Observable Discrepancy •

CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 0

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. Se detectó un problema de tipo XSS en Zammad versiones 3.0 hasta 3.2. Un usuario poco privilegiado puede proporcionar código malicioso por medio de la funcionalidad de Carga de Archivos en Zammad. • https://zammad.com/news/security-advisory-zaa-2020-02 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0

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. Se detectó un problema en Zammad versiones 3.0 hasta 3.2. Después de la autenticación, transmite información confidencial al usuario que puede ser comprometida y usada por un atacante para conseguir acceso no autorizado. • https://zammad.com/news/security-advisory-zaa-2020-04 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0

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) Se detectó un problema en Zammad versiones 3.0 hasta 3.2. Devuelve el código fuente de recursos estáticos al enviar una petición OPTIONS, en lugar de una petición GET. • https://zammad.com/news/security-advisory-zaa-2020-09 • CWE-552: Files or Directories Accessible to External Parties •

CVSS: 6.1EPSS: 0%CPEs: 1EXPL: 0

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. Las versiones 2.3.0 y anteriores de Zammad GmbH Zammad contienen una vulnerabilidad de neutralización incorrecta de etiquetas HTML relacionadas con scripts en una página web (CWE-80) en el asunto de correos electrónicos que no están entrecomillados por HTML en ciertos casos. • https://github.com/zammad/zammad/issues/1869 https://zammad.com/news/release-2-4 https://zammad.com/news/security-advisory-zaa-2018-01 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •