{"answers":{"affected":"3 open source packages ship an affected version, including through. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-29940 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-29940 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-29940 is a critical 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-29940 and fix it if it is affected.\n\nWhat it is: CVE-2021-29940 is a critical 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-29940 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- through (crates.io): affected all versions up to 0.1.0; no fix listed\n- through (crates.io): affected all versions up to 0.1.0; no fix listed\n- through (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-29940/ (Markdown: https://insights.sbomify.com/CVE-2021-29940/index.md)","id":"CVE-2021-29940","markdown":"https://insights.sbomify.com/CVE-2021-29940/index.md","name":"CVE-2021-29940","record":{"aliases":["GHSA-5hpj-m323-cphm","RUSTSEC-2021-0049"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust through crate","requires_auth":"none","summary":"A double free vulnerability in the Rust through crate allows attackers to cause denial of service or potentially execute code via a panic in the map function.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"through","vendor":"through_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-415","name":"Double Free"}],"description":"An issue was discovered in the through crate through 2021-02-18 for Rust. There is a double free (in through and through_and) upon a panic of the map 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 through","id":"CVE-2021-29940","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 reorder","id":"CVE-2021-29941"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.0"],"package":"through","purl":null,"source":"GHSA-5hpj-m323-cphm"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.0"],"package":"through","purl":"pkg:cargo/through","source":"GHSA-5hpj-m323-cphm"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"through","purl":"pkg:cargo/through","source":"RUSTSEC-2021-0049"}],"prev":{"headline":"Out of bounds write in stackvector","id":"CVE-2021-29939"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"A double free vulnerability in the Rust through crate allows attackers to cause denial of service or potentially execute code via a panic in the map function.","url":"https://insights.sbomify.com/CVE-2021-29940/"}