dbcve.org
ZabbixApplication

CVE-2023-29458

HIGH · 7.5 CVSS v3.1 Published 2023-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Duktape is an 3rd-party embeddable JavaScript engine, with a focus on portability and compact footprint. When adding too many values in valstack JavaScript will crash. This issue occurs due to bug in Duktape 2.6 which is an 3rd-party solution that we use.

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

Duktape 2.6 contains a bug in its value stack (valstack) implementation where adding too many JavaScript values causes a crash, leading to denial of service. This is a boundary condition error in the 3rd-party JavaScript engine's memory management.

MitigationUpdate Duktape to a patched version that fixes the valstack boundary handling, or implement application-level limits on value stack depth to prevent the crash condition.

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.34= 6.0.17= 6.4.2

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

CVSS:3.1/AV:N/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. Confirm Zabbix is installed
    Check for Zabbix processes or packages: 'ps aux | grep zabbix' or 'rpm -qa | grep zabbix' / 'dpkg -l | grep zabbix'
    Affected if No Zabbix process or package found means not affected
  2. Identify the Zabbix version
    Run 'zabbix_server -V' or 'zabbix_agentd -V' to get the installed version number
    Affected if Version equals exactly 5.0.34, 6.0.17, or 6.4.2 - other versions are not affected
  3. Verify Duktape JavaScript engine is enabled
    Check Zabbix configuration for 'LoadModule' directives loading duktape or javascript support, or check for JavaScript-preprocessing items in use
    Affected if If Duktape is not loaded or JavaScript preprocessing is not used, the crash cannot be triggered
  4. Check for active JavaScript item parameters or scripts
    Review Zabbix item configurations for 'JavaScript' preprocessing or userparameter scripts that execute JavaScript code
    Affected if Only Zabbix installations actively processing JavaScript with the affected versions are vulnerable

Only Zabbix versions 5.0.34, 6.0.17, or 6.4.2 with Duktape/JavaScript preprocessing enabled and actively processing JavaScript are affected by this vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Duktape to a patched version that fixes the valstack boundary handling, or implement application-level limits on value stack depth to prevent the crash condition.

Recommended fix Moderate confidence

Zabbix 5.0.35+/6.0.18+/6.4.3+ (or latest available 6.0/6.4/7.0 release)

  1. Identify the currently running Zabbix version using `zabbix_server --version` or checking the web UI footer
  2. For Zabbix 5.0.x users: Upgrade to Zabbix 5.0.35 or later (preferably 5.0 LTS recent patch)
  3. For Zabbix 6.0.x users: Upgrade to Zabbix 6.0.18 or later
  4. For Zabbix 6.4.x users: Upgrade to a later 6.4 release if available, or migrate to Zabbix 6.0 LTS or 7.0
  5. After upgrade, verify the Duktape library version included in the new release includes the valstack fix
  6. Test JavaScript functionality in Zabbix (e.g., item preprocessing, user scripts) to confirm normal operation
Caveat Review Zabbix upgrade notes for your version path - some upgrades may require database schema updates; 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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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