{"answers":{"affected":"3 open source packages ship an affected version, including heapless. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36464 in the wild and no public exploit code.","fix":"Upgrade heapless to 0.6.1 or later.","what":"CVE-2020-36464 is a high-severity use after free vulnerability in n/a, published on 8 Aug 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-2020-36464 and fix it if it is affected.\n\nWhat it is: CVE-2020-36464 is a high-severity use after free vulnerability in n/a, published on 8 Aug 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-2020-36464 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- heapless (crates.io): affected all versions; fixed in 0.6.1\n- heapless (crates.io): affected all versions; fixed in 0.6.1\n- heapless (crates.io): affected from 0.0.0-0; fixed in 0.6.1\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-2020-36464/ (Markdown: https://insights.sbomify.com/CVE-2020-36464/index.md)","id":"CVE-2020-36464","markdown":"https://insights.sbomify.com/CVE-2020-36464/index.md","name":"CVE-2020-36464","record":{"aliases":["GHSA-qgwf-r2jj-2ccv","RUSTSEC-2020-0145"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust heapless crate","requires_auth":"none","summary":"A use-after-free vulnerability in the heapless crate allows attackers to cause memory corruption or crashes via improper cloning of partially consumed iterators.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"heapless","vendor":"heapless_project"}],"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-416","name":"Use After Free"}],"description":"An issue was discovered in the heapless crate before 0.6.1 for Rust. The IntoIter Clone implementation clones an entire underlying Vec without considering whether it has already been partially consumed.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Use after free in heapless","id":"CVE-2020-36464","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Use after free in generic-array","id":"CVE-2020-36465"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0"],"last_affected":[],"package":"heapless","purl":null,"source":"GHSA-qgwf-r2jj-2ccv"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0"],"last_affected":[],"package":"heapless","purl":"pkg:cargo/heapless","source":"GHSA-qgwf-r2jj-2ccv"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"heapless","purl":"pkg:cargo/heapless","source":"RUSTSEC-2020-0145"}],"prev":{"headline":"Data races in multiqueue","id":"CVE-2020-36463"},"products":["n/a"],"published":"2021-08-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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-04","vendors":["n/a"]},"summary":"A use-after-free vulnerability in the heapless crate allows attackers to cause memory corruption or crashes via improper cloning of partially consumed iterators.","url":"https://insights.sbomify.com/CVE-2020-36464/"}