Vulnerability record · CVE-2017-5619 · published 13 March 2017
CVE-2017-5619: Zammad improper authentication vulnerability
Zammad · Zammad
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.
Description
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.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/96937 | Third Party AdvisoryVDB Entry |
| https://zammad.com/de/news/security-advisory-zaa-2017-01 | Vendor Advisory |
| http://www.securityfocus.com/bid/96937 | Third Party AdvisoryVDB Entry |
| https://zammad.com/de/news/security-advisory-zaa-2017-01 | Vendor Advisory |
Track CVE-2017-5619 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2017-5619), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.