CVE-2024-36466: Unauthenticated Zabbix frontend takeover when SSO is being used
Noroxi assessment
Priority: Monitor (action score 35/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.72% (FIRST EPSS); higher than 54.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Zabbix Zabbix 6.0.32rc1, 6.4.17rc1.
Low priority for now. Upgrade to Zabbix Zabbix 6.0.32rc1, 6.4.17rc1 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
A bug in the code allows an attacker to sign a forged zbx_session cookie, which then allows them to sign in with admin permissions.
- Published
- Nov 28, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-290
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Zabbix
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Is your version affected? Check itNoroxi 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 |
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
- 7.0.0affected
- 6.0.0 and later · up to and including 6.0.31affected · gitfixed in 6.0.32rc1
- 6.4.0 and later · up to and including 6.4.16affected · gitfixed in 6.4.17rc1
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zabbix zabbix6.0.0 and later · before 6.0.32
- zabbix zabbix6.4.0 and later · before 6.4.17
- zabbix zabbix7.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | zabbix | from 0 | — |
| Debian:13 | zabbix | before 1:7.0.1+dfsg-1 | 1:7.0.1+dfsg-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…64This week
Published before and after this one in the same product
- ← EarlierCVE-2024-42333Nov 27, 2024 · Heap buffer over-read10Monitor
- ← EarlierCVE-2024-36464Nov 27, 2024 · Media Types: Office365, SMTP passwords are unencrypted and visible in plaintext when exported10Monitor
- Later →CVE-2024-36465Apr 2, 2025 · SQL injection in Zabbix API46Plan
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 | 6.0.32rc1 | Vendor (CNA) |
| Zabbix Zabbix | 6.4.17rc1 | Vendor (CNA) |
| debian:zabbix | 1:7.0.1+dfsg-1 · Debian:13 | 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-423271 days apartSQL injection in user.get API63This week
- CVE-2024-22122108 days apartAT(GSM) Command Injection36Monitor
- CVE-2024-22116108 days apartRemote code execution within ping script28Monitor
- CVE-2024-22123108 days apartZabbix Arbitrary File Read10Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-290 · Authentication Bypass by SpoofingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-461High
- Signature SpoofCAPEC-473
- Signature Spoofing by MisrepresentationCAPEC-476likelihood: Low · High
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- Masquerading: Invalid Code SignatureT1036.001
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls: Code SigningT1553.002
- Adversary-in-the-MiddleT1557
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.