{"answers":{"affected":"3 open source packages ship an affected version, including futures-util. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35908 in the wild and no public exploit code.","fix":"Upgrade futures-util to 0.3.2 or later.","what":"CVE-2020-35908 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-35908 and fix it if it is affected.\n\nWhat it is: CVE-2020-35908 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-35908 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- futures-util (crates.io): affected from 0.3.0; fixed in 0.3.2\n- futures-util (crates.io): affected from 0.3.0; fixed in 0.3.2\n- futures-util (crates.io): affected from 0.3.0; fixed in 0.3.2\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-35908/ (Markdown: https://insights.sbomify.com/CVE-2020-35908/index.md)","id":"CVE-2020-35908","markdown":"https://insights.sbomify.com/CVE-2020-35908/index.md","name":"CVE-2020-35908","record":{"aliases":["GHSA-5r9g-j7jj-hw6c","RUSTSEC-2020-0062"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust futures-util crate","requires_auth":"low_privilege","summary":"A race condition in the futures-util crate allows data corruption due to mishandled synchronization, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"future-utils","vendor":"rust-lang"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled.","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":"Improper `Sync` implementation on `FuturesUnordered` in futures-utils can cause data corruption","id":"CVE-2020-35908","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":"Unexpected panic in multihash","id":"CVE-2020-35909"},"packages":[{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0.3.0"],"last_affected":[],"package":"futures-util","purl":null,"source":"GHSA-5r9g-j7jj-hw6c"},{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0.3.0"],"last_affected":[],"package":"futures-util","purl":"pkg:cargo/futures-util","source":"GHSA-5r9g-j7jj-hw6c"},{"ecosystem":"crates.io","fixed":["0.3.2"],"introduced":["0.3.0"],"last_affected":[],"package":"futures-util","purl":"pkg:cargo/futures-util","source":"RUSTSEC-2020-0062"}],"prev":{"headline":"futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer","id":"CVE-2020-35907"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":4.7,"headline":"MutexGuard::map can cause a data race in safe code","id":"CVE-2020-35905","kev_date_added":null,"published":"2020-12-31"}],"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 race condition in the futures-util crate allows data corruption due to mishandled synchronization, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2020-35908/"}