{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39343 exists.","fix":"No fix has been published for CVE-2022-39343 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39343 is a medium-severity vulnerability in azure-rtos filex, published on 8 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39343 and fix it if it is affected.\n\nWhat it is: CVE-2022-39343 is a medium-severity vulnerability in azure-rtos filex, published on 8 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39343 exists.\n\nAffected product: azure-rtos filex. 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-2022-39343/ (Markdown: https://insights.sbomify.com/CVE-2022-39343/index.md)","id":"CVE-2022-39343","markdown":"https://insights.sbomify.com/CVE-2022-39343/index.md","name":"CVE-2022-39343","record":{"aliases":["GHSA-8jqf-wjhq-4w9f"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Azure RTOS FileX","requires_auth":"none","summary":"Integer overflows in Azure RTOS FileX fault-tolerant feature allow buffer overflows and memory modification via crafted log files.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"azure_rtos_filex","vendor":"microsoft"}],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Azure RTOS FileX is a FAT-compatible file system that’s fully integrated with Azure RTOS ThreadX. In versions before 6.2.0, the Fault Tolerant feature of Azure RTOS FileX includes integer under and overflows which may be exploited to achieve buffer overflow and modify memory contents. When a valid log file with correct ID and checksum is detected by the `_fx_fault_tolerant_enable` function an attempt to recover the previous failed write operation is taken by call of `_fx_fault_tolerant_apply_logs`. This function iterates through the log entries and performs required recovery operations. When properly crafted a log including entries of type `FX_FAULT_TOLERANT_DIR_LOG_TYPE` may be utilized to introduce unexpected behavior. This issue has been patched in version 6.2.0. A workaround to fix line 218 in fx_fault_tolerant_apply_logs.c is documented in the GHSA.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Azure RTOS FileX vulnerable to Buffer Offerflow","id":"CVE-2022-39343","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Azure RTOS USBX vulnerable to buffer overflow","id":"CVE-2022-39344"},"packages":[],"prev":{"headline":"OpenFGA Authorization Bypass","id":"CVE-2022-39342"},"products":["filex"],"published":"2022-11-08","related":[],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["azure-rtos"]},"summary":"Integer overflows in Azure RTOS FileX fault-tolerant feature allow buffer overflows and memory modification via crafted log files.","url":"https://insights.sbomify.com/CVE-2022-39343/"}