CVE-2024-36461: Direct access to memory pointers within the JS engine for modification
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.75% (FIRST EPSS); higher than 55.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.31rc1, 6.4.16rc1, 7.0.1rc1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Zabbix Zabbix 6.0.31rc1, 6.4.16rc1, 7.0.1rc1 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
Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine.
- Published
- Aug 12, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- CWE-822
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
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · Zabbix
- 9.1
- 0.3 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
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
- 6.0.0 and later · up to and including 6.0.30affected · gitfixed in 6.0.31rc1
- 6.4.0 and later · up to and including 6.4.15affected · gitfixed in 6.4.16rc1
- 7.0.0alpha1 and later · up to and including 7.0.0affected · gitfixed in 7.0.1rc1
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 · up to 6.0.30 inclusive
- zabbix zabbix6.4.0 and later · up to 6.4.15 inclusive
- 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 |
| openSUSE:Leap 15.6 | zabbix | before 6.0.33-bp156.2.3.1 | 6.0.33-bp156.2.3.1 |
| openSUSE:Tumbleweed | zabbix | before 6.0.33-1.1 | 6.0.33-1.1 |
| SUSE:Package Hub 15 SP6 | zabbix | before 6.0.33-bp156.2.3.1 | 6.0.33-bp156.2.3.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-22123Aug 12, 2024 · Zabbix Arbitrary File Read10Monitor
- ← EarlierCVE-2024-36460Aug 12, 2024 · Front-end audit log shows passwords in plaintext32Monitor
- Later →CVE-2024-36462Aug 12, 2024 · Allocation of resources without limits or throttling (uncontrolled resource consumption)30Monitor
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.31rc1 | Vendor (CNA) |
| Zabbix Zabbix | 6.4.16rc1 | Vendor (CNA) |
| Zabbix Zabbix | 7.0.1rc1 | Vendor (CNA) |
| debian:zabbix | 1:7.0.1+dfsg-1 · Debian:13 | Package registry (OSV) |
| opensuse:zabbix | 6.0.33-bp156.2.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:zabbix | 6.0.33-bp156.2.3.1 · SUSE:Package Hub 15 SP6 | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1211 · Aug 13, 2024(Zabbix Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · 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-822 · Untrusted Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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)
ATT&CK techniques
—
Change log (1)
- 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.