{"answers":{"affected":"3 open source packages ship an affected version, including conqueue. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36437 in the wild and no public exploit code.","fix":"Upgrade conqueue to 0.4.0 or later.","what":"CVE-2020-36437 is a high-severity 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-36437 and fix it if it is affected.\n\nWhat it is: CVE-2020-36437 is a high-severity 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-36437 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- conqueue (crates.io): affected all versions; fixed in 0.4.0\n- conqueue (crates.io): affected all versions; fixed in 0.4.0\n- conqueue (crates.io): affected from 0.0.0-0; fixed in 0.4.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-36437/ (Markdown: https://insights.sbomify.com/CVE-2020-36437/index.md)","id":"CVE-2020-36437","markdown":"https://insights.sbomify.com/CVE-2020-36437/index.md","name":"CVE-2020-36437","record":{"aliases":["GHSA-368f-29c3-4f2r","RUSTSEC-2020-0117"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust concurrency library","requires_auth":"none","summary":"Unconditional Send and Sync implementations in the conqueue crate allow data races, potentially leading to memory corruption or crashes in Rust applications.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"conqueue","vendor":"conqueue_project"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"An issue was discovered in the conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and Sync for QueueSender\u003cT\u003e.","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 race in conqueue","id":"CVE-2020-36437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Data race in tiny_future","id":"CVE-2020-36438"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"conqueue","purl":null,"source":"GHSA-368f-29c3-4f2r"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"conqueue","purl":"pkg:cargo/conqueue","source":"GHSA-368f-29c3-4f2r"},{"ecosystem":"crates.io","fixed":["0.4.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"conqueue","purl":"pkg:cargo/conqueue","source":"RUSTSEC-2020-0117"}],"prev":{"headline":"Data races in unicycle","id":"CVE-2020-36436"},"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":"Unconditional Send and Sync implementations in the conqueue crate allow data races, potentially leading to memory corruption or crashes in Rust applications.","url":"https://insights.sbomify.com/CVE-2020-36437/"}