{"answers":{"affected":"3 open source packages ship an affected version, including obstack. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35894 in the wild and no public exploit code.","fix":"Upgrade obstack to 0.1.4 or later.","what":"CVE-2020-35894 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-35894 and fix it if it is affected.\n\nWhat it is: CVE-2020-35894 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-35894 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- obstack (crates.io): affected all versions; fixed in 0.1.4\n- obstack (crates.io): affected all versions; fixed in 0.1.4\n- obstack (crates.io): affected from 0.0.0-0; fixed in 0.1.4\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-35894/ (Markdown: https://insights.sbomify.com/CVE-2020-35894/index.md)","id":"CVE-2020-35894","markdown":"https://insights.sbomify.com/CVE-2020-35894/index.md","name":"CVE-2020-35894","record":{"aliases":["GHSA-85j6-f8j6-q26x","RUSTSEC-2020-0040"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust obstack crate","requires_auth":"none","summary":"Unaligned references in the Rust obstack crate can lead to memory corruption, potentially allowing code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"obstack","vendor":"obstack_project"}],"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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"An issue was discovered in the obstack crate before 0.1.4 for Rust. Unaligned references 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":true,"headline":"Unaligned references in Obstack","id":"CVE-2020-35894","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":"Out-of-bounds write in stack","id":"CVE-2020-35895"},"packages":[{"ecosystem":"crates.io","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"obstack","purl":null,"source":"GHSA-85j6-f8j6-q26x"},{"ecosystem":"crates.io","fixed":["0.1.4"],"introduced":["0"],"last_affected":[],"package":"obstack","purl":"pkg:cargo/obstack","source":"GHSA-85j6-f8j6-q26x"},{"ecosystem":"crates.io","fixed":["0.1.4"],"introduced":["0.0.0-0"],"last_affected":[],"package":"obstack","purl":"pkg:cargo/obstack","source":"RUSTSEC-2020-0040"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-35893"},"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":"Unaligned references in the Rust obstack crate can lead to memory corruption, potentially allowing code execution or crashes.","url":"https://insights.sbomify.com/CVE-2020-35894/"}