{"answers":{"affected":"3 open source packages ship an affected version, including autorand. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36210 in the wild and no public exploit code.","fix":"Upgrade autorand to 0.2.3 or later.","what":"CVE-2020-36210 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 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-2020-36210 and fix it if it is affected.\n\nWhat it is: CVE-2020-36210 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 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-2020-36210 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- autorand (crates.io): affected all versions; fixed in 0.2.3\n- autorand (crates.io): affected all versions; fixed in 0.2.3\n- autorand (crates.io): affected from 0.0.0-0; fixed in 0.2.3\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-36210/ (Markdown: https://insights.sbomify.com/CVE-2020-36210/index.md)","id":"CVE-2020-36210","markdown":"https://insights.sbomify.com/CVE-2020-36210/index.md","name":"CVE-2020-36210","record":{"aliases":["GHSA-cgmg-2v6m-fjg7","RUSTSEC-2020-0103"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust autorand crate","requires_auth":"low_privilege","summary":"Attackers can trigger memory corruption via uninitialized memory drops during panics in the Rust autorand crate, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"autorand","vendor":"autorand_project"}],"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":[{"id":"CWE-908","name":"Use of Uninitialized Resource"},{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in the autorand crate before 0.2.3 for Rust. Because of impl Random on arrays, uninitialized memory can be dropped when a panic occurs, leading to memory corruption.","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":"Free of uninitialized memory in autorand","id":"CVE-2020-36210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Data races in gfwx","id":"CVE-2020-36211"},"packages":[{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"autorand","purl":null,"source":"GHSA-cgmg-2v6m-fjg7"},{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"autorand","purl":"pkg:cargo/autorand","source":"GHSA-cgmg-2v6m-fjg7"},{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"autorand","purl":"pkg:cargo/autorand","source":"RUSTSEC-2020-0103"}],"prev":{"headline":"Data races in late-static","id":"CVE-2020-36209"},"products":["n/a"],"published":"2021-01-22","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":"Attackers can trigger memory corruption via uninitialized memory drops during panics in the Rust autorand crate, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2020-36210/"}