Skip to content
Fencer Intel
critical 9.1

CVE-2024-36461 json

Direct access to memory pointers within the JS engine for modification

published 2y ago modified 4mo ago also EUVD-2024-36105

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine.

Patch / fix

  • zabbix zabbix 6.0.31rc1, 6.4.16rc1, 7.0.0rc3
  • zabbix zabbix_server 6.0.31rc1, 6.4.16rc1, 7.0.0rc3
  • zabbix Debian 14, Debian 13 1:7.0.1+dfsg-1

debian advisories DEBIAN-CVE-2024-36461

  • zabbix Package Hub 15 SP6, openSUSE Leap 15.6 6.0.33-bp156.2.3.1
  • zabbix openSUSE Tumbleweed 6.0.33-1.1

opensuse advisories openSUSE-SU-2024:0384-1openSUSE-SU-2024:14356-1

Is CVE-2024-36461 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-36461 updated cvss 9.1

zabbix: irect access to memory pointers within the JS engine for modification

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Zabbix Zabbix

Classification

Weakness
  • CWE-822 Untrusted Pointer Dereference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.