CVE-2024-36469: User enumeration via timing attack in Zabbix web interface
Noroxi assessment
Priority: Monitor (action score 9/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Zabbix Zabbix 5.0.46rc1, 6.0.38rc1, 7.0.9rc1.
Low priority for now. Upgrade to Zabbix Zabbix 5.0.46rc1, 6.0.38rc1, 7.0.9rc1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one.
- Published
- Apr 2, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-208
Report tools
Action score
9
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Zabbix
- 2.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zabbix | zabbix | cpe:2.3:a:zabbix:zabbix |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zabbix zabbix5.0.0 and later · before 5.0.46
- zabbix zabbix6.0.0 and later · before 6.0.38
- zabbix zabbix7.0.0 and later · before 7.0.9
- zabbix zabbix7.2.0 and later · before 7.2.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Zabbix). Independent of NVD's CPE analysis and usually ahead of it.
Zabbix Zabbix
- 5.0.0 and later · up to and including 5.0.45affected · gitfixed in 5.0.46rc1
- 6.0.0 and later · up to and including 6.0.37affected · gitfixed in 6.0.38rc1
- 7.0.0 and later · up to and including 7.0.8affected · gitfixed in 7.0.9rc1
- 7.2.0 and later · up to and including 7.2.2affected · gitfixed in 7.2.3rc1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | zabbix | before 1:5.0.46+dfsg-1+deb11u1 | 1:5.0.46+dfsg-1+deb11u1 |
| Debian:12 | zabbix | from 0 | — |
| Debian:13 | zabbix | before 1:7.0.9+dfsg-1 | 1:7.0.9+dfsg-1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | zabbix | before 4.0.12-4.45.1 | 4.0.12-4.45.1 |
Same product
zabbix: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23131Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAMLKEV98Now
- CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV80Now
- CVE-2016-10134SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the t64This week
Published before and after this one in the same product
- ← EarlierCVE-2024-36466Nov 28, 2024 · Unauthenticated Zabbix frontend takeover when SSO is being used35Monitor
- ← EarlierCVE-2024-36465Apr 2, 2025 · SQL injection in Zabbix API46Plan
- Later →CVE-2024-42325Apr 2, 2025 · Excessive information returned by user.get8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Zabbix Zabbix | 5.0.46rc1 | Vendor (CNA) |
| Zabbix Zabbix | 6.0.38rc1 | Vendor (CNA) |
| Zabbix Zabbix | 7.0.9rc1 | Vendor (CNA) |
| Zabbix Zabbix | 7.2.3rc1 | Vendor (CNA) |
| debian:zabbix | 1:7.0.9+dfsg-1 · Debian:13 | Package registry (OSV) |
| suse:zabbix | 4.0.12-4.45.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Jens Just Iversen (jensji)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-208 · Observable Timing DiscrepancyCVSS vector
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.