CVE-2024-36469: User enumeration via timing attack in Zabbix web interface
First published: Wed Apr 02 2025(Updated: )
Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one.
Credit: security@zabbix.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zabbix |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-36469?
CVE-2024-36469 has a moderate severity level due to the potential for timing attacks on login credentials.
How do I fix CVE-2024-36469?
To fix CVE-2024-36469, ensure that the application has consistent timing responses for both valid and invalid login attempts.
Which software versions are affected by CVE-2024-36469?
CVE-2024-36469 affects all versions of Zabbix, especially those that do not implement uniform response times.
Can CVE-2024-36469 lead to account compromise?
Yes, CVE-2024-36469 can lead to account compromise by allowing attackers to discern valid usernames.
What kind of attack is associated with CVE-2024-36469?
CVE-2024-36469 is associated with timing attacks that exploit the difference in response times during login attempts.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/title
- agent/type
- agent/first-publish-date
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/source
- agent/last-modified-date
- agent/tags
- agent/event
- vendor/zabbix
- canonical/zabbix