{"answers":{"affected":"3 open source packages ship an affected version, including aovec. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36207 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36207 is a high-severity 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-36207 and fix it if it is affected.\n\nWhat it is: CVE-2020-36207 is a high-severity 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-36207 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aovec (crates.io): affected all versions up to 1.1.0; no fix listed\n- aovec (crates.io): affected all versions up to 1.1.0; no fix listed\n- aovec (crates.io): affected from 0.0.0-0; no fix listed\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-36207/ (Markdown: https://insights.sbomify.com/CVE-2020-36207/index.md)","id":"CVE-2020-36207","markdown":"https://insights.sbomify.com/CVE-2020-36207/index.md","name":"CVE-2020-36207","record":{"aliases":["GHSA-g489-xrw3-3v8w","RUSTSEC-2020-0099"],"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 aovec crate","requires_auth":"low_privilege","summary":"A data race in the aovec crate allows memory corruption, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"aovec","vendor":"aovec_project"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 aovec crate through 2020-12-10 for Rust. Because Aovec\u003cT\u003e does not have bounds on its Send trait or Sync trait, a data race and 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":false,"headline":"Data races in aovec","id":"CVE-2020-36207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Data races in conquer-once","id":"CVE-2020-36208"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.1.0"],"package":"aovec","purl":null,"source":"GHSA-g489-xrw3-3v8w"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.1.0"],"package":"aovec","purl":"pkg:cargo/aovec","source":"GHSA-g489-xrw3-3v8w"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"aovec","purl":"pkg:cargo/aovec","source":"RUSTSEC-2020-0099"}],"prev":{"headline":"Data races in rusb","id":"CVE-2020-36206"},"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":"A data race in the aovec crate allows memory corruption, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2020-36207/"}