CVE-2024-42331 | Use after free in browser_push_error

In the src/libs/zbxembed/browser.c file, the es_browser_ctor method retrieves a heap pointer from the Duktape JavaScript engine. This heap pointer is subsequently utilized by the browser_push_error method in the src/libs/zbxembed/browser_error.c file. A use-after-free bug can occur at this stage if the wd->browser heap pointer is freed by garbage collection.

Published: 2024-11-27 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-42331 is rated Low Risk (19.3/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.26%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-42331

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.26% +0.24%
2 2026-01-05 0.05% 0.02% -0.03%
3 2025-05-07 — 0.05% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-42331

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 1.4 [email protected]

Weakness enumeration for CVE-2024-42331

OS Trackers for CVE-2024-42331

vendor priority summary link
alpine — CVE-2024-42331: 1 source package rows (zabbix); 2 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 2. https://security.alpinelinux.org/vuln/CVE-2024-42331
debian not yet assigned CVE-2024-42331 not yet assigned priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-42331
suse low CVE-2024-42331 severity low: SUSE including 2 source package names (zabbix, zabbix-agent), 7 product×package rows across 5 product lines (SUSE Linux Enterprise Server 12 SP4-LTSS, SUSE Linux Enterprise Server 12 SP5-LTSS, … (5 product lines)): Known Not Affected 7. https://www.suse.com/security/cve/CVE-2024-42331/
ubuntu medium CVE-2024-42331 medium priority: Ubuntu including 1 source packages (zabbix), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 5, not-affected 2, DNE 1, ignored 1, released 1. https://ubuntu.com/security/CVE-2024-42331

Affected software / configurations for CVE-2024-42331

Vendor Product Version Raw CPE
zabbix zabbix >= 7.0.0, < 7.0.4 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*

References for CVE-2024-42331

cvelogic Threat Intelligence