{"answers":{"affected":"2 open source packages ship an affected version, including arr. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35887 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35887 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35887 is a critical 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-35887 and fix it if it is affected.\n\nWhat it is: CVE-2020-35887 is a critical 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-35887 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- arr (crates.io): affected all versions up to 0.6.1; no fix listed\n- arr (crates.io): affected all versions up to 0.6.1; 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-35887/ (Markdown: https://insights.sbomify.com/CVE-2020-35887/index.md)","id":"CVE-2020-35887","markdown":"https://insights.sbomify.com/CVE-2020-35887/index.md","name":"CVE-2020-35887","record":{"aliases":["GHSA-fhvj-7f9p-w788"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust arr crate","requires_auth":"none","summary":"A buffer overflow in the Rust arr crate allows attackers to cause memory corruption, 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":"arr","vendor":"arr_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-120","name":"Buffer Copy without Checking Size of Input"}],"description":"An issue was discovered in the arr crate through 2020-08-25 for Rust. There is a buffer overflow in Index and IndexMut.","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":"Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr","id":"CVE-2020-35887","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-35888"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.6.1"],"package":"arr","purl":null,"source":"GHSA-fhvj-7f9p-w788"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.6.1"],"package":"arr","purl":"pkg:cargo/arr","source":"GHSA-fhvj-7f9p-w788"}],"prev":{"headline":"Race condition in n/a","id":"CVE-2020-35886"},"products":["n/a"],"published":"2020-12-31","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2020-35888","kev_date_added":null,"published":"2020-12-31"},{"cvss_score":4.7,"headline":"Race condition in n/a","id":"CVE-2020-35886","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":"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 buffer overflow in the Rust arr crate allows attackers to cause memory corruption, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2020-35887/"}