{"answers":{"affected":"3 open source packages ship an affected version, including atom. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35897 in the wild and no public exploit code.","fix":"Upgrade atom to 0.3.6 or later.","what":"CVE-2020-35897 is a medium-severity vulnerability in n/a, published on 31 Dec 2020. 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-35897 and fix it if it is affected.\n\nWhat it is: CVE-2020-35897 is a medium-severity vulnerability in n/a, published on 31 Dec 2020. 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-35897 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- atom (crates.io): affected all versions; fixed in 0.3.6\n- atom (crates.io): affected all versions; fixed in 0.3.6\n- atom (crates.io): affected from 0.0.0-0; fixed in 0.3.6\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-35897/ (Markdown: https://insights.sbomify.com/CVE-2020-35897/index.md)","id":"CVE-2020-35897","markdown":"https://insights.sbomify.com/CVE-2020-35897/index.md","name":"CVE-2020-35897","record":{"aliases":["GHSA-9cg2-2j2h-59v9","RUSTSEC-2020-0044"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust atom crate","requires_auth":"low_privilege","summary":"A race condition in the Rust atom crate allows cross-thread data races, potentially leading to memory corruption or data inconsistency.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"atom","vendor":"atom_project"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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 atom crate before 0.3.6 for Rust. An unsafe Send implementation allows a cross-thread data race.","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 atom","id":"CVE-2020-35897","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":"Use after free in actix-utils","id":"CVE-2020-35898"},"packages":[{"ecosystem":"crates.io","fixed":["0.3.6"],"introduced":["0"],"last_affected":[],"package":"atom","purl":null,"source":"GHSA-9cg2-2j2h-59v9"},{"ecosystem":"crates.io","fixed":["0.3.6"],"introduced":["0"],"last_affected":[],"package":"atom","purl":"pkg:cargo/atom","source":"GHSA-9cg2-2j2h-59v9"},{"ecosystem":"crates.io","fixed":["0.3.6"],"introduced":["0.0.0-0"],"last_affected":[],"package":"atom","purl":"pkg:cargo/atom","source":"RUSTSEC-2020-0044"}],"prev":{"headline":"Insufficient size checks in ws","id":"CVE-2020-35896"},"products":["n/a"],"published":"2020-12-31","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 race condition in the Rust atom crate allows cross-thread data races, potentially leading to memory corruption or data inconsistency.","url":"https://insights.sbomify.com/CVE-2020-35897/"}