{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-2214 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-2214 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2214 is a high-severity memory corruption vulnerability in Eclipse Foundation ThreadX, published on 26 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-2214 and fix it if it is affected.\n\nWhat it is: CVE-2024-2214 is a high-severity memory corruption vulnerability in Eclipse Foundation ThreadX, published on 26 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-2214 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation ThreadX. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-2214/ (Markdown: https://insights.sbomify.com/CVE-2024-2214/index.md)","id":"CVE-2024-2214","markdown":"https://insights.sbomify.com/CVE-2024-2214/index.md","name":"CVE-2024-2214","record":{"aliases":["GHSA-vmp6-qhp9-r66x"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RTOS kernel","requires_auth":"none","summary":"A missing array size check in the Xtensa port of Eclipse ThreadX allows memory overwrites, potentially leading to code execution or denial of service.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"threadx","vendor":"eclipse"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"In Eclipse ThreadX before version 6.4.0, the _Mtxinit() function in the \nXtensa port was missing an array size check causing a memory overwrite. \nThe affected file was ports/xtensa/xcc/src/tx_clib_lock.c","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing array size check in _Mtxinit() in the Xtensa port","id":"CVE-2024-2214","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Jenkins docker-build-step Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2024-2215"},"packages":[],"prev":{"headline":"Improper Authentication in zenml-io/zenml","id":"CVE-2024-2213"},"products":["ThreadX"],"published":"2024-03-26","related":[{"cvss_score":7.8,"headline":"Memory corruption in Eclipse ThreadX","id":"CVE-2026-0648","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":7.3,"headline":"Integer overflow in ThreadX","id":"CVE-2024-2212","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":7.2,"headline":"Improper Parameter Check in ThreadX Syscall Implementation","id":"CVE-2025-55080","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":5.7,"headline":"Missing check for thread priority","id":"CVE-2025-55079","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":5.7,"headline":"Incomplete validation of kernel object pointers in system calls","id":"CVE-2025-55078","kev_date_added":null,"published":"2025-10-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Eclipse Foundation"]},"summary":"A missing array size check in the Xtensa port of Eclipse ThreadX allows memory overwrites, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2024-2214/"}