dbcve.org
ZabbixApplication

CVE-2024-36463

HIGH · 8.8 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 5.0.43 / 6.0.33 or later.
See remediation →
94/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 implementation of atob in "Zabbix JS" allows to create a string with arbitrary content and use it to access internal 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 atob function in Zabbix JS has a vulnerability that allows creating strings with arbitrary content that can be used to access internal properties of objects. This is likely a prototype pollution or similar JavaScript object property access flaw in Zabbix's custom JavaScript engine implementation.

MitigationApply the vendor patch for CVE-2024-36463 to the Zabbix JS component to fix the atob implementation and prevent unauthorized property access.

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.0.43>= 6.0.0, < 6.0.33>= 6.4.0, < 6.4.18>= 7.0.0, < 7.0.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Zabbix version
    Run 'zabbix_server -V' or 'zabbix_agentd -V' to get the installed version, or check the web interface footer
    Affected if The version falls within >= 5.0.0 and < 5.0.43, OR >= 6.0.0 and < 6.0.33, OR >= 6.4.0 and < 6.4.18, OR >= 7.0.0 and < 7.0.3
  2. Verify JavaScript preprocessing is in use
    Query the database for items with JavaScript preprocessing: SELECT itemid, key_, js_lld FROM items WHERE js_lld IS NOT NULL AND js_lld != ''; Or check Zabbix UI under item preprocessing configuration
    Affected if Any items, LLD rules, or calculated items have JavaScript preprocessing steps configured
  3. Check for atob usage in preprocessing
    Search the database for atob function calls in preprocessing scripts: SELECT * FROM item_preproc WHERE params LIKE '%atob%';
    Affected if Any JavaScript preprocessing step uses the atob function with untrusted input
  4. Inspect JavaScript engine configuration
    Check zabbix_server.conf for JavaScript related settings, and verify that the JS engine is enabled for item preprocessing (it is enabled by default)
    Affected if Zabbix server has JavaScript preprocessing enabled (default behavior) and the version is in the affected range

A user is affected if they run a vulnerable Zabbix version (5.0.0-5.0.42, 6.0.0-6.0.32, 6.4.0-6.4.17, or 7.0.0-7.0.2) AND have items using JavaScript preprocessing with the atob function handling external or untrusted data.

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.0.43 / 6.0.33 / 6.4.18 or later
Fixed in 5.0.436.0.336.4.18
Interim mitigation

Apply the vendor patch for CVE-2024-36463 to the Zabbix JS component to fix the atob implementation and prevent unauthorized property access.

Recommended fix High confidence

Upgrade to Zabbix 5.0.43, 6.0.33, 6.4.18, or 7.0.3 (or later) depending on your current major branch

  1. Identify all Zabbix components in your environment (server, proxy, agent, frontend)
  2. Download the appropriate Zabbix installation packages for your target fixed version from official.zabbix.com or your package repository
  3. Stop Zabbix server, proxy, and agent services before upgrading
  4. Upgrade Zabbix server and proxy to the fixed version (5.0.43+, 6.0.33+, 6.4.18+, or 7.0.3+)
  5. Upgrade Zabbix agents on all monitored hosts to matching version
  6. Upgrade Zabbix frontend (PHP) to matching version
  7. Review and apply any database schema changes required by the new version (zabbix_server --foreground --config <config_file> --DBUpgradeForce may be needed)
  8. Start Zabbix services in correct order: server first, then proxy, then agents
Caveat Review Zabbix release notes for breaking changes; minor version upgrades within the same major version typically have minimal breaking changes, but test in staging first

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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