{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43997 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43997 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43997 is a high-severity vulnerability in n/a, published on 17 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43997 and fix it if it is affected.\n\nWhat it is: CVE-2021-43997 is a high-severity vulnerability in n/a, published on 17 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43997 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-43997/ (Markdown: https://insights.sbomify.com/CVE-2021-43997/index.md)","id":"CVE-2021-43997","markdown":"https://insights.sbomify.com/CVE-2021-43997/index.md","name":"CVE-2021-43997","record":{"aliases":["GHSA-cp2g-q9qc-pm45"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"RTOS kernel","requires_auth":"low_privilege","summary":"Attackers with code execution can escalate privileges in FreeRTOS by bypassing MPU protections in ARMv7-M and ARMv8-M ports.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"freertos","vendor":"amazon"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"FreeRTOS versions 10.2.0 through 10.4.5 do not prevent non-kernel code from calling the xPortRaisePrivilege internal function to raise privilege. FreeRTOS versions through 10.4.6 do not prevent a third party that has already independently gained the ability to execute injected code to achieve further privilege escalation by branching directly inside a FreeRTOS MPU API wrapper function with a manually crafted stack frame. These issues affect ARMv7-M MPU ports, and ARMv8-M ports with MPU support enabled (i.e. configENABLE_MPU set to 1). These are fixed in V10.5.0 and in V10.4.3-LTS Patch 3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2021-43997","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"HashiCorp Vault Incorrect Permission Assignment for Critical Resource","id":"CVE-2021-43998"},"packages":[],"prev":{"headline":"Incorrect Access Control in Ignition","id":"CVE-2021-43996"},"products":["n/a"],"published":"2021-11-17","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-32020","kev_date_added":null,"published":"2021-05-03"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2021-31571","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2021-31572","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":9.3,"headline":"Improper input validation in FreeRTOS-Kernel timer command handling","id":"CVE-2026-77234","kev_date_added":null,"published":"2026-08-21"},{"cvss_score":8.8,"headline":"Privilege Escalation in FreeRTOS Kernel ARMv7-M MPU ports and ARMv8-M ports with MPU support enabled","id":"CVE-2024-28115","kev_date_added":null,"published":"2024-03-07"},{"cvss_score":8.3,"headline":"Missing privilege check in SecureContext_FreeContext in FreeRTOS-Kernel","id":"CVE-2026-77235","kev_date_added":null,"published":"2026-08-21"},{"cvss_score":8.3,"headline":"Missing size validation in SecureContext_AllocateContext in FreeRTOS-Kernel","id":"CVE-2026-77236","kev_date_added":null,"published":"2026-08-21"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers with code execution can escalate privileges in FreeRTOS by bypassing MPU protections in ARMv7-M and ARMv8-M ports.","url":"https://insights.sbomify.com/CVE-2021-43997/"}