{"answers":{"affected":"3 open source packages ship an affected version, including atomic-option. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36219 is a medium-severity 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-36219 and fix it if it is affected.\n\nWhat it is: CVE-2020-36219 is a medium-severity 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-36219 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- atomic-option (crates.io): affected all versions up to 0.1.2; no fix listed\n- atomic-option (crates.io): affected all versions up to 0.1.2; no fix listed\n- atomic-option (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-36219/ (Markdown: https://insights.sbomify.com/CVE-2020-36219/index.md)","id":"CVE-2020-36219","markdown":"https://insights.sbomify.com/CVE-2020-36219/index.md","name":"CVE-2020-36219","record":{"aliases":["GHSA-8gf5-q9p9-wvmc","RUSTSEC-2020-0113"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust atomic-option crate","requires_auth":"none","summary":"A data race in the atomic-option crate can lead to undefined behavior due to incorrect Sync implementation, affecting Rust applications using this library.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"atomic-option","vendor":"atomic-option_project"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in the atomic-option crate through 2020-10-31 for Rust. Because AtomicOption\u003cT\u003e implements Sync unconditionally, a data race 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 race in atomic-option","id":"CVE-2020-36219","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 race in va-ts","id":"CVE-2020-36220"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.2"],"package":"atomic-option","purl":null,"source":"GHSA-8gf5-q9p9-wvmc"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.2"],"package":"atomic-option","purl":"pkg:cargo/atomic-option","source":"GHSA-8gf5-q9p9-wvmc"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"atomic-option","purl":"pkg:cargo/atomic-option","source":"RUSTSEC-2020-0113"}],"prev":{"headline":"Improper synchronization in buttplug","id":"CVE-2020-36218"},"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":"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 atomic-option crate can lead to undefined behavior due to incorrect Sync implementation, affecting Rust applications using this library.","url":"https://insights.sbomify.com/CVE-2020-36219/"}