Username enumeration via unequal login rejection timing
Published Apr 2, 2025 · Updated Nov 3, 2025
Observable timing discrepancy in affected Zabbix 5.0, 6.0, 7.0, and 7.2 releases allows remote attackers to enumerate valid usernames. The frontend login form and unauthenticated user.login API take measurably different time to reject existing and nonexistent usernames; Zabbix has not published the underlying code path. Access to the frontend or API and repeated measurements are required, while five consecutive frontend failures trigger a 30-second pause; the bounded consequence is disclosure of valid account names.
Summary
What happened
Observable timing discrepancy in affected Zabbix 5.0, 6.0, 7.0, and 7.2 releases allows remote attackers to enumerate valid usernames. The frontend login form and unauthenticated user.login API take measurably different time to reject existing and nonexistent usernames; Zabbix has not published the underlying code path. Access to the frontend or API and repeated measurements are required, while five consecutive frontend failures trigger a 30-second pause; the bounded consequence is disclosure of valid account names.
The record
- CVE
- CVE-2024-36469
- Published
- Apr 2, 2025
- Updated
- Nov 3, 2025
- Vendor
- Zabbix
- Product
- Zabbix
- Classifications
- CWE-208, CAPEC-462, T1087
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0.0 <=5.0.45 changes=[{"at":"5.0.46rc1","status":"unaffected"}]
- Affected versionversion=6.0.0 <=6.0.37 changes=[{"at":"6.0.38rc1","status":"unaffected"}]
- Affected versionversion=7.0.0 <=7.0.8 changes=[{"at":"7.0.9rc1","status":"unaffected"}]
- Affected versionversion=7.2.0 <=7.2.2 changes=[{"at":"7.2.3rc1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo