Cyber Resilience

CVE-2023-29458

Zabbix 5.0.34 … 6.4.2

Published
13 July 2023
Modified
03 November 2025
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.0076 52th percentile
Risk Priority 47 floored blend · peak EPSS

Summary

CVE-2023-29458 is a medium-severity Improper Validation of Array Index (CWE-129) vulnerability in Zabbix Zabbix. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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…

more

we use.

CWE(s)
CWE-129

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-32722Same product: Zabbix Zabbix
CVE-2024-42331Same product: Zabbix Zabbix
CVE-2024-36461Same product: Zabbix Zabbix
CVE-2024-36468Same product: Zabbix Zabbix
CVE-2024-42326Same product: Zabbix Zabbix
CVE-2023-29451Same product: Zabbix Zabbix
CVE-2024-42330Same product: Zabbix Zabbix
CVE-2024-22117Same product: Zabbix Zabbix
CVE-2024-22120Same product: Zabbix Zabbix
CVE-2024-22119Same product: Zabbix Zabbix

Affected Assets

zabbix
zabbix
5.0.34, 6.0.17, 6.4.2

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.

A.8.26 Application security requirements partial match
prevents

Application security requirements include validation of untrusted input used for indexing or addressing memory structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.

References