{"answers":{"affected":"3 open source packages ship an affected version, including stackvector. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-29939 in the wild and no public exploit code.","fix":"Upgrade stackvector to 1.0.9 or later.","what":"CVE-2021-29939 is a high-severity memory corruption 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-29939 and fix it if it is affected.\n\nWhat it is: CVE-2021-29939 is a high-severity memory corruption 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-29939 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stackvector (crates.io): affected all versions; fixed in 1.0.9\n- stackvector (crates.io): affected all versions; fixed in 1.0.9\n- stackvector (crates.io): affected from 0.0.0-0; fixed in 1.0.9\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-29939/ (Markdown: https://insights.sbomify.com/CVE-2021-29939/index.md)","id":"CVE-2021-29939","markdown":"https://insights.sbomify.com/CVE-2021-29939/index.md","name":"CVE-2021-29939","record":{"aliases":["DEBIAN-CVE-2021-29939","GHSA-9frf-r7c7-j2vg","RUSTSEC-2021-0048","UBUNTU-CVE-2021-29939"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust stackvector crate","requires_auth":"none","summary":"An out-of-bounds write in the Rust stackvector 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":"stackvector","vendor":"stackvector_project"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in the stackvector crate through 2021-02-19 for Rust. There is an out-of-bounds write in StackVec::extend if size_hint provides certain anomalous data.","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":"Out of bounds write in stackvector","id":"CVE-2021-29939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Double free in through","id":"CVE-2021-29940"},"packages":[{"ecosystem":"crates.io","fixed":["1.0.9"],"introduced":["0"],"last_affected":[],"package":"stackvector","purl":null,"source":"GHSA-9frf-r7c7-j2vg"},{"ecosystem":"crates.io","fixed":["1.0.9"],"introduced":["0"],"last_affected":[],"package":"stackvector","purl":"pkg:cargo/stackvector","source":"GHSA-9frf-r7c7-j2vg"},{"ecosystem":"crates.io","fixed":["1.0.9"],"introduced":["0.0.0-0"],"last_affected":[],"package":"stackvector","purl":"pkg:cargo/stackvector","source":"RUSTSEC-2021-0048"}],"prev":{"headline":"Double free in slice-deque","id":"CVE-2021-29938"},"products":["n/a"],"published":"2021-04-01","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-19","vendors":["n/a"]},"summary":"An out-of-bounds write in the Rust stackvector crate allows attackers to cause memory corruption, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2021-29939/"}