{"answers":{"affected":"3 open source packages ship an affected version, including hashconsing. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36215 in the wild and no public exploit code.","fix":"Upgrade hashconsing to 1.1.0 or later.","what":"CVE-2020-36215 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 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-36215 and fix it if it is affected.\n\nWhat it is: CVE-2020-36215 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 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-36215 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hashconsing (crates.io): affected all versions; fixed in 1.1.0\n- hashconsing (crates.io): affected all versions; fixed in 1.1.0\n- hashconsing (crates.io): affected from 0.0.0-0; fixed in 1.1.0\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-36215/ (Markdown: https://insights.sbomify.com/CVE-2020-36215/index.md)","id":"CVE-2020-36215","markdown":"https://insights.sbomify.com/CVE-2020-36215/index.md","name":"CVE-2020-36215","record":{"aliases":["GHSA-rw2c-c256-3r53","RUSTSEC-2020-0107"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust hashconsing crate","requires_auth":"none","summary":"Attackers can trigger memory corruption in the Rust hashconsing crate due to missing Send/Sync bounds, 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":"hashconsing","vendor":"hashconsing_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-787","name":"Out-of-bounds Write"},{"id":"CWE-662","name":"Improper Synchronization"}],"description":"An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.","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":"Data races in hashconsing","id":"CVE-2020-36215","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 race in eventio","id":"CVE-2020-36216"},"packages":[{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"hashconsing","purl":null,"source":"GHSA-rw2c-c256-3r53"},{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"hashconsing","purl":"pkg:cargo/hashconsing","source":"GHSA-rw2c-c256-3r53"},{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"hashconsing","purl":"pkg:cargo/hashconsing","source":"RUSTSEC-2020-0107"}],"prev":{"headline":"Data races in multiqueue2","id":"CVE-2020-36214"},"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 in the Rust hashconsing crate due to missing Send/Sync bounds, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2020-36215/"}