dbcve.org
ZabbixApplication

CVE-2024-42328

MEDIUM · 5.5 CVSS v3.1 Published 2024-11-27
Fix available
A fix is available. Upgrade to 7.0.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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
When the webdriver for the Browser object downloads data from a HTTP server, the data pointer is set to NULL and is allocated only in curl_write_cb when receiving data. If the server's response is an empty document, then wd->data in the code below will remain NULL and an attempt to read from it will result in a crash.

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

A NULL pointer dereference vulnerability exists in the Browser object's webdriver when handling HTTP responses. When downloading data from an HTTP server, the data pointer is initially set to NULL and only allocated in the curl_write_cb callback when data is received. If the server returns an empty document, the data pointer remains NULL, causing a crash when the code attempts to read from it.

MitigationImplement a NULL check before dereferencing the wd->data pointer, or ensure proper initialization of the data buffer even when handling empty HTTP responses.

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:>= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify Zabbix installation and version
    Run command: zabbix_server --version or check package manager (dpkg -l | grep zabbix, rpm -qa | grep zabbix)
    Affected if Version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.4 (versions >= 7.0.0 and < 7.0.4)
  2. Identify if Browser webdriver is configured
    Check Zabbix configuration files (zabbix_server.conf) for webdriver or Browser-related parameters, or look for web scenarios using the browser item type
    Affected if Browser item type or webdriver functionality is enabled in Zabbix front-end or templates
  3. Check for crash logs related to HTTP response handling
    Search system logs (journalctl, /var/log/messages, /var/log/zabbix/zabbix_server.log) for NULL pointer dereference errors or segfaults occurring during web scenario or browser monitoring operations
    Affected if Crashes are logged mentioning curl_write_cb, webdriver, or NULL dereference in browser-related operations
  4. Inspect active web scenarios using browser monitoring
    In Zabbix front-end, navigate to Monitoring > Web or use API (zabbix_api) to list web scenarios that use the Browser item type
    Affected if Any web scenarios are configured with Browser item type (not just HTTP agent)

You are affected if Zabbix server version is 7.0.0 through 7.0.4 and Browser/webdriver monitoring is actively used for web scenarios, or if crash logs show NULL pointer dereference in browser-related HTTP handling.

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 7.0.4 or later
Fixed in 7.0.4
Interim mitigation

Implement a NULL check before dereferencing the wd->data pointer, or ensure proper initialization of the data buffer even when handling empty HTTP responses.

Recommended fix Moderate confidence

Zabbix 7.0.4 or later

  1. Identify current Zabbix version using 'zabbix_server --version' or checking the web interface
  2. Plan maintenance window for the upgrade
  3. Back up Zabbix database and configuration files
  4. Stop Zabbix server and related services
  5. Upgrade Zabbix to version 7.0.4 or later using official package repositories or source
  6. Verify the upgrade was successful
  7. Restart Zabbix services
  8. Confirm the Browser item/webdriver functionality works correctly with non-empty responses
Caveat Review Zabbix 7.0.x release notes for any breaking changes between your current minor version and 7.0.4

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42328 — 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-42328 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