Cyber Resilience

CVE-2024-2214

Eclipse Threadx ≤ 6.4.0

Published
26 March 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0034 26th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2024-2214 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Eclipse Threadx. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

In Eclipse ThreadX before version 6.4.0, the _Mtxinit() function in the Xtensa port was missing an array size check causing a memory overwrite. The affected file was ports/xtensa/xcc/src/tx_clib_lock.c

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-2026-0648Same product: Eclipse Threadx
CVE-2024-2212Same product: Eclipse Threadx
CVE-2025-55078Same product: Eclipse Threadx
CVE-2025-55080Same product: Eclipse Threadx
CVE-2025-55079Same product: Eclipse Threadx
CVE-2025-14549Same vendor: Eclipse
CVE-2025-55082Same vendor: Eclipse
CVE-2025-55085Same vendor: Eclipse
CVE-2026-16243Same vendor: Eclipse
CVE-2026-6918Same vendor: Eclipse

Affected Assets

eclipse
threadx
≤ 6.4.0

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