Back to Database
Status published
Critical
CVE-2017-5619
An issue was discovered in Zammad before 1.0.4, 1.1.x before...
Vulnerability 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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2017-5619
Credits & Attribution
No credits recorded in the NVD database.
References
More from zammad
View All →CVE-2022-48023
Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker...
Medium
4.3
CVE-2022-48022
An issue in the component /api/v1/mentions of Zammad v5.3.0 allows...
Unknown
0
CVE-2022-48021
A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary...
Unknown
0
CVE-2022-40817
Zammad 5.2.1 has a fine-grained permission model that allows to...
Unknown
0
CVE-2022-40816
Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset...
Unknown
0
Affected Vendor
zammad
View all reports →Affected Software
zammad
Vulnerable Versions:
0, 1.1.0, 1.1.1, 1.1.2, 1.2.0
Timeline
Official Publish:
March 13th, 2017
Last Modified:
August 5th, 2024
Added to House:
July 20th, 2026
CVSS Vectors
V3:
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.