{"answers":{"affected":"3 open source packages ship an affected version, including slice-deque. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20995 in the wild and no public exploit code.","fix":"Upgrade slice-deque to 0.1.16 or later.","what":"CVE-2018-20995 is a critical memory corruption vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20995 and fix it if it is affected.\n\nWhat it is: CVE-2018-20995 is a critical memory corruption vulnerability in n/a, published on 26 Aug 2019. 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-2018-20995 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- slice-deque (crates.io): affected all versions; fixed in 0.1.16\n- slice-deque (crates.io): affected all versions; fixed in 0.1.16\n- slice-deque (crates.io): affected from 0.0.0-0; fixed in 0.1.16\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-2018-20995/ (Markdown: https://insights.sbomify.com/CVE-2018-20995/index.md)","id":"CVE-2018-20995","markdown":"https://insights.sbomify.com/CVE-2018-20995/index.md","name":"CVE-2018-20995","record":{"aliases":["GHSA-hr3c-6mmp-6m39","RUSTSEC-2018-0008"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust slice-deque crate","requires_auth":"none","summary":"Attackers can trigger memory corruption in the slice-deque Rust 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":"slice-deque","vendor":"slice-deque_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in the slice-deque crate before 0.1.16 for Rust. move_head_unchecked allows memory corruption because deque updates are 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":"Memory corruption slice-deque","id":"CVE-2018-20995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":3,"n_references":1,"next":{"headline":"Double free in crossbeam","id":"CVE-2018-20996"},"packages":[{"ecosystem":"crates.io","fixed":["0.1.16"],"introduced":["0"],"last_affected":[],"package":"slice-deque","purl":null,"source":"GHSA-hr3c-6mmp-6m39"},{"ecosystem":"crates.io","fixed":["0.1.16"],"introduced":["0"],"last_affected":[],"package":"slice-deque","purl":"pkg:cargo/slice-deque","source":"GHSA-hr3c-6mmp-6m39"},{"ecosystem":"crates.io","fixed":["0.1.16"],"introduced":["0.0.0-0"],"last_affected":[],"package":"slice-deque","purl":"pkg:cargo/slice-deque","source":"RUSTSEC-2018-0008"}],"prev":{"headline":"Uncontrolled recursion in trust-dns-proto","id":"CVE-2018-20994"},"products":["n/a"],"published":"2019-08-26","related":[{"cvss_score":9.8,"headline":"Out of bounds write in slice-deque","id":"CVE-2019-15543","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":7.5,"headline":"Double free in slice-deque","id":"CVE-2021-29938","kev_date_added":null,"published":"2021-04-01"}],"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-05","vendors":["n/a"]},"summary":"Attackers can trigger memory corruption in the slice-deque Rust library, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2018-20995/"}