dbcve.org
ZabbixApplication

CVE-2024-42330

CRITICAL · 9.1 CVSS v3.1 Published 2024-11-27
Fix available
A fix is available. Upgrade to 5.4.6 / 6.0.34 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The HttpRequest object returns HTTP response headers as strings without proper JavaScript encoding. Since these strings are created directly from server-supplied data, an attacker can craft malicious header values containing special characters or escape sequences that enable access to hidden object properties, potentially leading to prototype pollution or data exfiltration.

MitigationImplement proper JavaScript encoding/escaping of all string values returned from HttpRequest headers before using them in object property access or string operations. Validate and sanitize header content at the application boundary.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZabbixApplication
Affected:>= 5.0.0, < 5.4.6>= 6.0.0, < 6.0.34>= 6.4.0, < 6.4.19>= 7.0.0, < 7.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Zabbix version
    Run 'zabbix_server --version' or 'zabbix_proxy --version' on the server, or check the Zabbix web interface footer for the version number
    Affected if The installed version falls within any of these ranges: 5.0.0 to 5.4.5, 6.0.0 to 6.0.33, 6.4.0 to 6.4.18, or 7.0.0 to 7.0.3
  2. Locate HTTP agent items or web scenarios
    In Zabbix web UI, go to Configuration > Hosts > Items and filter for type 'HTTP agent', or check Configuration > Web scenarios for any monitored HTTP services
    Affected if Any HTTP agent items or web scenarios exist that retrieve external HTTP responses
  3. Identify items using JavaScript preprocessing with header access
    Review item preprocessing configurations for any JavaScript steps that access response headers, such as 'JSONPath' with header data or custom JavaScript that calls HttpRequest() and processes headers
    Affected if JavaScript preprocessing is used to process HTTP response headers from HttpRequest calls
  4. Check for userparameter scripts or external script integrations
    Review /etc/zabbix/zabbix_server.conf for 'ExternalScripts' directory and examine any custom scripts in that directory that may use the Zabbix JavaScript API to make HTTP requests
    Affected if Custom external scripts or userparameters leverage the HttpRequest functionality to fetch and process HTTP headers

You are affected if your Zabbix version is within the affected ranges AND you use HTTP agent items, web scenarios, or custom JavaScript preprocessing that processes HTTP response headers via HttpRequest.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.6 / 6.0.34 / 6.4.19 or later
Fixed in 5.4.66.0.346.4.19
Interim mitigation

Implement proper JavaScript encoding/escaping of all string values returned from HttpRequest headers before using them in object property access or string operations. Validate and sanitize header content at the application boundary.

Recommended fix High confidence

Upgrade to Zabbix 5.4.6, 6.0.34, 6.4.19, or 7.0.4 (or later) depending on your current major version branch

  1. Backup your current Zabbix database and configuration files
  2. Plan a maintenance window for the upgrade
  3. Review Zabbix upgrade documentation for your current version at https://www.zabbix.com/documentation/
  4. Stop Zabbix server and frontend services
  5. Upgrade Zabbix packages using your package manager (e.g., yum update zabbix-server-mysql, apt get upgrade zabbix-server-mysql)
  6. Or download and install from https://www.zabbix.com/download_sources
  7. Start Zabbix server and verify all services are running
  8. Clear browser cache and test the web frontend
Caveat Review Zabbix release notes for your target version as minor upgrades typically have minimal breaking changes but always test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zabbix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA4.0 h
23.0 hours of engineering $4,020
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42330 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data