dbcve.org
ZabbixApplication

CVE-2024-45700

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-02
Fix available
A fix is available. Upgrade to 6.0.39 / 7.0.10 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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
Zabbix server is vulnerable to a DoS vulnerability due to uncontrolled resource exhaustion. An attacker can send specially crafted requests to the server, which will cause the server to allocate an excessive amount of memory and perform CPU-intensive decompression operations, ultimately leading to a service 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

Zabbix server contains a denial-of-service vulnerability stemming from uncontrolled resource exhaustion during decompression operations. An attacker can send specially crafted requests that trigger excessive memory allocation and CPU-intensive decompression, causing the server to crash. The vulnerability affects the Zabbix server component and requires no authentication to exploit.

MitigationApply the vendor-supplied patch or update to a non-vulnerable Zabbix version. Additionally, implement rate limiting and request throttling on network boundaries to mitigate the impact of malicious decompression requests.

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:>= 6.0.0, < 6.0.39>= 7.0.0, < 7.0.10>= 7.2.0, < 7.2.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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. Identify Zabbix server installation
    Check if Zabbix server is installed by running 'zabbix_server --version' or checking for the zabbix-server process with 'ps aux | grep zabbix'
    Affected if Zabbix server is not installed or not running
  2. Determine installed Zabbix server version
    Run 'zabbix_server --version' to display the version number, or check the package manager output with 'dpkg -l | grep zabbix' or 'rpm -qa | grep zabbix'
    Affected if The version falls within any of these ranges: 6.0.0 to 6.0.38, 7.0.0 to 7.0.9, or 7.2.0 to 7.2.3
  3. Verify Zabbix web interface is enabled
    Check if the Zabbix web frontend is configured and accessible by examining web server configuration files (e.g., /etc/zabbix/web/zabbix.conf.php) or by attempting to access the Zabbix web URL
    Affected if The web interface is exposed and accessible, as network requests are the attack vector for this vulnerability
  4. Confirm server is network-accessible
    Review network configuration to determine if the Zabbix server frontend port (typically 8080 or 80 for HTTP, 443 for HTTPS) is listening on a non-localhost interface using 'netstat -tlnp | grep zabbix' or 'ss -tlnp | grep zabbix'
    Affected if The Zabbix web interface is bound to a public or untrusted network interface, allowing unauthenticated attackers to send malicious decompression requests

A system is affected if it runs a Zabbix server version 6.0.0-6.0.38, 7.0.0-7.0.9, or 7.2.0-7.2.3 with the web interface network-accessible to untrusted users.

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 6.0.39 / 7.0.10 / 7.2.4 or later
Fixed in 6.0.397.0.107.2.4
Interim mitigation

Apply the vendor-supplied patch or update to a non-vulnerable Zabbix version. Additionally, implement rate limiting and request throttling on network boundaries to mitigate the impact of malicious decompression requests.

Recommended fix High confidence

Upgrade to Zabbix 6.0.39, 7.0.10, or 7.2.4 depending on your current major version branch

  1. 1. Back up the Zabbix database and all configuration files before upgrading.
  2. 2. Stop the Zabbix server, Zabbix agent, and related services.
  3. 3. For Zabbix 6.0.x: Upgrade to version 6.0.39. For Zabbix 7.0.x: Upgrade to version 7.0.10. For Zabbix 7.2.x: Upgrade to version 7.2.4.
  4. 4. Update the Zabbix repository to the appropriate version and run the package upgrade command (e.g., `apt update && apt install zabbix-server-mysql zabbix-frontend-php` for Debian/Ubuntu, or `yum update zabbix-server-mysql` for RHEL/CentOS).
  5. 5. Verify the database schema is up to date by running the migration scripts if required.
  6. 6. Start the Zabbix server and verify it is running without errors.
  7. 7. Confirm the vulnerability is patched by checking the Zabbix server version matches the fixed release.
Caveat Review Zabbix release notes for any breaking changes between your current version and the target fixed version before upgrading

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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