{"answers":{"affected":"3 open source packages ship an affected version, including array-tools. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36452 in the wild and no public exploit code.","fix":"Upgrade array-tools to 0.3.2 or later.","what":"CVE-2020-36452 is a critical memory corruption 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-36452 and fix it if it is affected.\n\nWhat it is: CVE-2020-36452 is a critical memory corruption 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-36452 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- array-tools (crates.io): affected all versions; fixed in 0.3.2\n- array-tools (crates.io): affected all versions; fixed in 0.3.2\n- array-tools (crates.io): affected from 0.0.0-0; fixed in 0.3.2\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-36452/ (Markdown: https://insights.sbomify.com/CVE-2020-36452/index.md)","id":"CVE-2020-36452","markdown":"https://insights.sbomify.com/CVE-2020-36452/index.md","name":"CVE-2020-36452","record":{"aliases":["GHSA-6wp2-fw3v-mfmc","RUSTSEC-2020-0132"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust array-tools crate","requires_auth":"none","summary":"A memory corruption vulnerability in the Rust array-tools crate allows attackers to cause crashes or potentially execute code via uninitialized memory drops.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"array-tools","vendor":"array-tools_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the array-tools crate before 0.3.2 for Rust. FixedCapacityDequeLike::clone() has a drop of uninitialized memory.","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":"Memory corruption in array-tools","id":"CVE-2020-36452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Data races in scottqueue","id":"CVE-2020-36453"},"packages":[{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0"],"last_affected":[],"package":"array-tools","purl":null,"source":"GHSA-6wp2-fw3v-mfmc"},{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0"],"last_affected":[],"package":"array-tools","purl":"pkg:cargo/array-tools","source":"GHSA-6wp2-fw3v-mfmc"},{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"array-tools","purl":"pkg:cargo/array-tools","source":"RUSTSEC-2020-0132"}],"prev":{"headline":"Data races in rcu_cell","id":"CVE-2020-36451"},"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 memory corruption vulnerability in the Rust array-tools crate allows attackers to cause crashes or potentially execute code via uninitialized memory drops.","url":"https://insights.sbomify.com/CVE-2020-36452/"}