CVE-2017-5619
UnknownEPSS 1.54%
Last modified
CVE-2017-5619 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.54% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Zammad | Zammad | <= 1.0.3 |
| Zammad | Zammad | 1.1.0 |
| Zammad | Zammad | 1.1.1 |
| Zammad | Zammad | 1.1.2 |
| Zammad | Zammad | 1.2.0 |
References
- http://www.securityfocus.com/bid/96937Third Party Advisory, VDB Entry
- https://zammad.com/de/news/security-advisory-zaa-2017-01Vendor Advisory
- http://www.securityfocus.com/bid/96937Third Party Advisory, VDB Entry
- https://zammad.com/de/news/security-advisory-zaa-2017-01Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5619?
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.
How severe is CVE-2017-5619?
Severity scoring for CVE-2017-5619 is pending analysis. The EPSS model estimates a 1.54% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5619?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2017-5619?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST