LiveActive security incident?Get immediate response
CVE Record

CVE-2023-29458: Duktape 2.6 bug crashes JavaScript putting too many values in valstack.

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability can crash Zabbix’s embedded JavaScript engine when too many values are pushed onto Duktape’s value stack. The main business risk is monitoring disruption, not data theft. Public evidence provided does not show active exploitation or a named vendor fix.

Executive priority

Treat this as a moderate operational resilience issue. It can affect monitoring availability, which may reduce incident visibility, but the provided evidence does not support emergency response for active exploitation.

Technical view

CVE-2023-29458 is a Duktape 2.6 valstack handling bug reported against Zabbix. The CVSS vector indicates network reachability, low privileges, high attack complexity, no user interaction, no confidentiality impact, low integrity impact, and high availability impact. The source bundle maps affected Zabbix versions to 5.0.0, 6.0.0, 6.4.0, and 7.0.0alpha1.

Likely exposure

Exposure is most likely in Zabbix environments running the listed affected versions and using functionality that invokes the bundled Duktape JavaScript engine. The source bundle does not describe exact feature paths, package builds, or configuration prerequisites.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source in the bundle states active exploitation. CVSS suggests exploitation requires authenticated low-privilege access and high complexity, with availability as the primary impact.

Researcher notes

Evidence is incomplete on the precise vulnerable call path and fixed versions. The CVSS vector and affected list come from the CVE bundle; mitigation should be anchored to Zabbix and Debian advisories rather than assumed Duktape-only replacement.

Mitigation direction

  • Inventory Zabbix versions against the affected releases listed in the CVE bundle.
  • Review Zabbix ZBX-22989 and Debian LTS guidance for vendor-supported fixes.
  • Prioritize upgrades or package updates once confirmed by vendor advisories.
  • Restrict low-privilege access to Zabbix features that execute JavaScript where operationally feasible.
  • Monitor Zabbix service crashes and availability alerts for unusual patterns.

Validation and detection

  • Confirm whether deployed Zabbix versions match 5.0.0, 6.0.0, 6.4.0, or 7.0.0alpha1.
  • Check installed Duktape or bundled JavaScript engine versions where package data exposes them.
  • Review Zabbix logs for crashes correlated with JavaScript processing activity.
  • Verify whether vendor advisories identify a fixed Zabbix or Debian package version.
  • Document compensating controls around authenticated Zabbix access and JavaScript-enabled workflows.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-129: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-29458 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H1.64.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-29458Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZabbixZabbix5,0,0, 6,0,0, 6.4.0, 7.0.0alpha1affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-129 · source CWE mapping

Improper Validation of Array Index

Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.