{"answers":{"affected":"3 open source packages ship an affected version, including rio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35876 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35876 is a critical use after free vulnerability in n/a, published on 31 Dec 2020. 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-35876 and fix it if it is affected.\n\nWhat it is: CVE-2020-35876 is a critical use after free vulnerability in n/a, published on 31 Dec 2020. 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-35876 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rio (crates.io): affected all versions up to 0.9.4; no fix listed\n- rio (crates.io): affected all versions up to 0.9.4; no fix listed\n- rio (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-35876/ (Markdown: https://insights.sbomify.com/CVE-2020-35876/index.md)","id":"CVE-2020-35876","markdown":"https://insights.sbomify.com/CVE-2020-35876/index.md","name":"CVE-2020-35876","record":{"aliases":["GHSA-8rc5-mr4f-m243","RUSTSEC-2020-0021"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust rio crate","requires_auth":"none","summary":"Attackers can exploit a leaked struct in the rio crate to cause use-after-free, data races, or information disclosure.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rio","vendor":"rio_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"},{"id":"CWE-416","name":"Use After Free"}],"description":"An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a 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":false,"headline":"Use after free in rio","id":"CVE-2020-35876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Out of bounds read in Ozone","id":"CVE-2020-35877"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.9.4"],"package":"rio","purl":null,"source":"GHSA-8rc5-mr4f-m243"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.9.4"],"package":"rio","purl":"pkg:cargo/rio","source":"GHSA-8rc5-mr4f-m243"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"rio","purl":"pkg:cargo/rio","source":"RUSTSEC-2020-0021"}],"prev":{"headline":"Excessive memory usage in tokio-rustls","id":"CVE-2020-35875"},"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":"Attackers can exploit a leaked struct in the rio crate to cause use-after-free, data races, or information disclosure.","url":"https://insights.sbomify.com/CVE-2020-35876/"}