{"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-2021-29938 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-29938 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-29938 is a high-severity use after free vulnerability in n/a, published on 1 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-29938 and fix it if it is affected.\n\nWhat it is: CVE-2021-29938 is a high-severity use after free vulnerability in n/a, published on 1 Apr 2021. 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-2021-29938 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- slice-deque (crates.io): affected all versions up to 0.3.0; no fix listed\n- slice-deque (crates.io): affected all versions up to 0.3.0; no fix listed\n- slice-deque (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-2021-29938/ (Markdown: https://insights.sbomify.com/CVE-2021-29938/index.md)","id":"CVE-2021-29938","markdown":"https://insights.sbomify.com/CVE-2021-29938/index.md","name":"CVE-2021-29938","record":{"aliases":["GHSA-p9gf-gmfv-398m","RUSTSEC-2021-0047"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust slice-deque crate","requires_auth":"none","summary":"A double drop vulnerability in the Rust slice-deque crate can cause memory corruption and potential code execution when a panic occurs during filtering.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slice-deque","vendor":"slice-deque_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:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"An issue was discovered in the slice-deque crate through 2021-02-19 for Rust. A double drop can occur in SliceDeque::drain_filter upon a panic in a predicate function.","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":"Double free in slice-deque","id":"CVE-2021-29938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Out of bounds write in stackvector","id":"CVE-2021-29939"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.3.0"],"package":"slice-deque","purl":null,"source":"GHSA-p9gf-gmfv-398m"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.3.0"],"package":"slice-deque","purl":"pkg:cargo/slice-deque","source":"GHSA-p9gf-gmfv-398m"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"slice-deque","purl":"pkg:cargo/slice-deque","source":"RUSTSEC-2021-0047"}],"prev":{"headline":"Free of uninitialized memory in telemetry","id":"CVE-2021-29937"},"products":["n/a"],"published":"2021-04-01","related":[{"cvss_score":9.8,"headline":"Memory corruption slice-deque","id":"CVE-2018-20995","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":9.8,"headline":"Out of bounds write in slice-deque","id":"CVE-2019-15543","kev_date_added":null,"published":"2019-08-26"}],"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-03","vendors":["n/a"]},"summary":"A double drop vulnerability in the Rust slice-deque crate can cause memory corruption and potential code execution when a panic occurs during filtering.","url":"https://insights.sbomify.com/CVE-2021-29938/"}