{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2021-27504 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-27504 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-27504 is a high-severity vulnerability in Texas Instruments CC32XX, published on 21 Nov 2023. 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-27504 and fix it if it is affected.\n\nWhat it is: CVE-2021-27504 is a high-severity vulnerability in Texas Instruments CC32XX, published on 21 Nov 2023. 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-27504 in the wild and no public exploit code.\n\nAffected product: Texas Instruments CC32XX. 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-27504/ (Markdown: https://insights.sbomify.com/CVE-2021-27504/index.md)","id":"CVE-2021-27504","markdown":"https://insights.sbomify.com/CVE-2021-27504/index.md","name":"CVE-2021-27504","record":{"aliases":["GHSA-6627-82c3-q8c9"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TI FreeRTOS devices","requires_auth":"none","summary":"An integer overflow in FreeRTOS malloc allows attackers to execute arbitrary code on affected Texas Instruments embedded devices.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"freertos","vendor":"amazon"},{"product":"simplelink_cc13xx_software_development_kit","vendor":"ti"},{"product":"simplelink_cc26xx_software_development_kit","vendor":"ti"},{"product":"simplelink_cc32xx_software_development_kit","vendor":"ti"},{"product":"simplelink_msp432e401y","vendor":"ti"},{"product":"simplelink_msp432e411y","vendor":"ti"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"Texas Instruments devices running FREERTOS, malloc returns a valid \npointer to a small buffer on extremely large values, which can trigger \nan integer overflow vulnerability in 'malloc' for FreeRTOS, resulting in\n code execution.","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":"Texas Instruments FREERTOS Integer Overflow or Wraparound","id":"CVE-2021-27504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"mySCADA myPRO Exposure of Information Through Directory Listing","id":"CVE-2021-27505"},"packages":[],"prev":{"headline":"Hardcoded credentials in Ypsomed mylife Cloud, mylife Mobile Application","id":"CVE-2021-27503"},"products":["CC32XX","SimpleLink MSP432E4XX","SimpleLink-CC13XX","SimpleLink-CC26XX","SimpleLink-CC32XX"],"published":"2023-11-21","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Texas Instruments"]},"summary":"An integer overflow in FreeRTOS malloc allows attackers to execute arbitrary code on affected Texas Instruments embedded devices.","url":"https://insights.sbomify.com/CVE-2021-27504/"}