{"answers":{"affected":"3 open source packages ship an affected version, including calamine. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-26951 in the wild and no public exploit code.","fix":"Upgrade calamine to 0.17.0 or later.","what":"CVE-2021-26951 is a critical memory corruption vulnerability in n/a, published on 9 Feb 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-26951 and fix it if it is affected.\n\nWhat it is: CVE-2021-26951 is a critical memory corruption vulnerability in n/a, published on 9 Feb 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-26951 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- calamine (crates.io): affected all versions; fixed in 0.17.0\n- calamine (crates.io): affected all versions; fixed in 0.17.0\n- calamine (crates.io): affected from 0.0.0-0; fixed in 0.17.0\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-26951/ (Markdown: https://insights.sbomify.com/CVE-2021-26951/index.md)","id":"CVE-2021-26951","markdown":"https://insights.sbomify.com/CVE-2021-26951/index.md","name":"CVE-2021-26951","record":{"aliases":["GHSA-ppqp-78xx-3r38","RUSTSEC-2021-0015"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust calamine crate","requires_auth":"none","summary":"Attackers can overwrite heap memory and execute arbitrary code via improper memory handling in the calamine Rust library.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"calamine","vendor":"calamine_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-908","name":"Use of Uninitialized Resource"},{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation, as demonstrated by Sectors::get.","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 calamine","id":"CVE-2021-26951","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":"Use of Uninitialized Resource in ms3d","id":"CVE-2021-26952"},"packages":[{"ecosystem":"crates.io","fixed":["0.17.0"],"introduced":["0"],"last_affected":[],"package":"calamine","purl":null,"source":"GHSA-ppqp-78xx-3r38"},{"ecosystem":"crates.io","fixed":["0.17.0"],"introduced":["0"],"last_affected":[],"package":"calamine","purl":"pkg:cargo/calamine","source":"GHSA-ppqp-78xx-3r38"},{"ecosystem":"crates.io","fixed":["0.17.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"calamine","purl":"pkg:cargo/calamine","source":"RUSTSEC-2021-0015"}],"prev":{"headline":"Memory corruption in Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products","id":"CVE-2021-26950"},"products":["n/a"],"published":"2021-02-09","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":"Attackers can overwrite heap memory and execute arbitrary code via improper memory handling in the calamine Rust library.","url":"https://insights.sbomify.com/CVE-2021-26951/"}