CVE-2024-42330 | JS - Internal strings in HTTP headers

The HttpRequest object allows to get the HTTP headers from the server's response after sending the request. The problem is that the returned strings are created directly from the data returned by the server and are not correctly encoded for JavaScript. This allows to create internal strings that can be used to access hidden properties of objects.

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-42330 is rated Moderate Risk (49.3/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.15%). Review affected assets and schedule remediation.

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-42330

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-01-16 0.14% 0.15% +0.01%
2 2026-01-05 0.30% 0.14% -0.16%
3 2025-11-30 — 0.30% —

Full EPSS history (12 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.3 6.0 [email protected]

Weakness enumeration for CVE-2024-42330

OS Trackers for CVE-2024-42330

vendor priority summary link
alpine — CVE-2024-42330: 1 source package rows (zabbix); 5 state rows across 3 repos (3.20-community, 3.22-community, edge-community); fixed 0, open 5. https://security.alpinelinux.org/vuln/CVE-2024-42330
debian not yet assigned CVE-2024-42330 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-42330
suse high CVE-2024-42330 severity important: 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-42330/
ubuntu medium CVE-2024-42330 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-42330

Affected software / configurations for CVE-2024-42330

Vendor Product Version Raw CPE
zabbix zabbix >= 5.0.0, < 5.4.6 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 6.0.0, < 6.0.34 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 6.4.0, < 6.4.19 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 7.0.0, < 7.0.4 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*

References for CVE-2024-42330

cvelogic Threat Intelligence