{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32032 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32032 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32032 is a high-severity memory corruption vulnerability in n/a, published on 21 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32032 and fix it if it is affected.\n\nWhat it is: CVE-2021-32032 is a high-severity memory corruption vulnerability in n/a, published on 21 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32032 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-32032/ (Markdown: https://insights.sbomify.com/CVE-2021-32032/index.md)","id":"CVE-2021-32032","markdown":"https://insights.sbomify.com/CVE-2021-32032/index.md","name":"CVE-2021-32032","record":{"aliases":["GHSA-2wjw-pc5m-j29q"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Trusted Firmware-M","requires_auth":"none","summary":"A memory leak in Trusted Firmware-M during failed cryptographic operations can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trusted_firmware-m","vendor":"trustedfirmware"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In Trusted Firmware-M through 1.3.0, cleaning up the memory allocated for a multi-part cryptographic operation (in the event of a failure) can prevent the abort() operation in the associated cryptographic library from freeing internal resources, causing a memory leak.","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":"Memory corruption in n/a","id":"CVE-2021-32032","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2021-32033"},"packages":[],"prev":{"headline":"ASUS Routers Improper Authentication","id":"CVE-2021-32030"},"products":["n/a"],"published":"2021-05-21","related":[{"cvss_score":5.5,"headline":"Arm Trusted Firmware Out-of-Bounds Write","id":"CVE-2021-27562","kev_date_added":"2021-11-03","published":"2021-05-25"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-43619","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2023-40271","kev_date_added":null,"published":"2023-09-08"},{"cvss_score":5.9,"headline":"Missing authorization in n/a","id":"CVE-2021-40327","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":4.7,"headline":"Information disclosure in n/a","id":"CVE-2023-51712","kev_date_added":null,"published":"2024-09-05"}],"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":["n/a"]},"summary":"A memory leak in Trusted Firmware-M during failed cryptographic operations can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2021-32032/"}