{"answers":{"affected":"3 open source packages ship an affected version, including rusb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36206 in the wild and no public exploit code.","fix":"Upgrade rusb to 0.7.0 or later.","what":"CVE-2020-36206 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-36206 and fix it if it is affected.\n\nWhat it is: CVE-2020-36206 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-36206 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rusb (crates.io): affected all versions; fixed in 0.7.0\n- rusb (crates.io): affected all versions; fixed in 0.7.0\n- rusb (crates.io): affected from 0.0.0-0; fixed in 0.7.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-36206/ (Markdown: https://insights.sbomify.com/CVE-2020-36206/index.md)","id":"CVE-2020-36206","markdown":"https://insights.sbomify.com/CVE-2020-36206/index.md","name":"CVE-2020-36206","record":{"aliases":["GHSA-9mxw-4856-9cm5","RUSTSEC-2020-0098"],"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 USB library","requires_auth":"low_privilege","summary":"A data race in the rusb crate can lead to memory corruption, allowing attackers to execute arbitrary code or cause denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rusb","vendor":"rusb_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 rusb crate before 0.7.0 for Rust. Because of a lack of Send and Sync bounds, 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":true,"headline":"Data races in rusb","id":"CVE-2020-36206","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 aovec","id":"CVE-2020-36207"},"packages":[{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"rusb","purl":null,"source":"GHSA-9mxw-4856-9cm5"},{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"rusb","purl":"pkg:cargo/rusb","source":"GHSA-9mxw-4856-9cm5"},{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"rusb","purl":"pkg:cargo/rusb","source":"RUSTSEC-2020-0098"}],"prev":{"headline":"Memory handling issues in xcb","id":"CVE-2020-36205"},"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 rusb crate can lead to memory corruption, allowing attackers to execute arbitrary code or cause denial of service.","url":"https://insights.sbomify.com/CVE-2020-36206/"}