{"answers":{"affected":"3 open source packages ship an affected version, including flatbuffers. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35864 in the wild and no public exploit code.","fix":"Upgrade flatbuffers to 2.0.0 or later.","what":"CVE-2020-35864 is a high-severity memory corruption 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-35864 and fix it if it is affected.\n\nWhat it is: CVE-2020-35864 is a high-severity memory corruption 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-35864 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- flatbuffers (crates.io): affected from 0.4.0; fixed in 2.0.0\n- flatbuffers (crates.io): affected from 0.4.0; fixed in 2.0.0\n- flatbuffers (crates.io): affected from 0.4.0; fixed in 2.0.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-35864/ (Markdown: https://insights.sbomify.com/CVE-2020-35864/index.md)","id":"CVE-2020-35864","markdown":"https://insights.sbomify.com/CVE-2020-35864/index.md","name":"CVE-2020-35864","record":{"aliases":["CLEANSTART-2024-CC98818","GHSA-c9h5-hf8r-m97x","RUSTSEC-2020-0009"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust flatbuffers crate","requires_auth":"none","summary":"Attackers can trigger memory corruption via unsafe transmutations in the Rust flatbuffers library, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flatbuffers","vendor":"google"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. read_scalar (and read_scalar_at) can transmute values without unsafe blocks.","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":"Dangling reference in flatbuffers","id":"CVE-2020-35864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"os_str_bytes relies on undefined behavior of `char::from_u32_unchecked`","id":"CVE-2020-35865"},"packages":[{"ecosystem":"crates.io","fixed":["2.0.0"],"introduced":["0.4.0"],"last_affected":[],"package":"flatbuffers","purl":null,"source":"GHSA-c9h5-hf8r-m97x"},{"ecosystem":"crates.io","fixed":["2.0.0"],"introduced":["0.4.0"],"last_affected":[],"package":"flatbuffers","purl":"pkg:cargo/flatbuffers","source":"GHSA-c9h5-hf8r-m97x"},{"ecosystem":"crates.io","fixed":["2.0.0"],"introduced":["0.4.0"],"last_affected":[],"package":"flatbuffers","purl":"pkg:cargo/flatbuffers","source":"RUSTSEC-2020-0009"}],"prev":{"headline":"HTTP Request Smuggling in hyper","id":"CVE-2020-35863"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":9.8,"headline":"Unsound casting in flatbuffers","id":"CVE-2019-25004","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":"Attackers can trigger memory corruption via unsafe transmutations in the Rust flatbuffers library, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2020-35864/"}