{"answers":{"affected":"2 open source packages ship an affected version, including messagepack-rs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-45693 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-45693 is a critical memory corruption vulnerability in n/a, published on 26 Dec 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-45693 and fix it if it is affected.\n\nWhat it is: CVE-2021-45693 is a critical memory corruption vulnerability in n/a, published on 26 Dec 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-45693 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- messagepack-rs (crates.io): affected all versions up to 0.8.1; no fix listed\n- messagepack-rs (crates.io): affected all versions up to 0.8.1; 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-45693/ (Markdown: https://insights.sbomify.com/CVE-2021-45693/index.md)","id":"CVE-2021-45693","markdown":"https://insights.sbomify.com/CVE-2021-45693/index.md","name":"CVE-2021-45693","record":{"aliases":["GHSA-jqjj-r4qp-x2gh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust messagepack library","requires_auth":"none","summary":"Attackers can trigger uninitialized memory reads in the messagepack-rs Rust crate, potentially exposing sensitive data or causing crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"messagepack-rs","vendor":"messagepack-rs_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"}],"description":"An issue was discovered in the messagepack-rs crate through 2021-01-26 for Rust. deserialize_string_primitive may read from uninitialized memory locations.","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":"Use of Uninitialized Resource in messagepack-rs.","id":"CVE-2021-45693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Window may read from uninitialized memory locations in rdiff","id":"CVE-2021-45694"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.8.1"],"package":"messagepack-rs","purl":null,"source":"GHSA-jqjj-r4qp-x2gh"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.8.1"],"package":"messagepack-rs","purl":"pkg:cargo/messagepack-rs","source":"GHSA-jqjj-r4qp-x2gh"}],"prev":{"headline":"Use of Uninitialized Resource in messagepack-rs.","id":"CVE-2021-45692"},"products":["n/a"],"published":"2021-12-26","related":[{"cvss_score":9.8,"headline":"Use of Uninitialized Resource in messagepack-rs.","id":"CVE-2021-45690","kev_date_added":null,"published":"2021-12-26"},{"cvss_score":9.8,"headline":"Use of Uninitialized Resource in messagepack-rs","id":"CVE-2021-45691","kev_date_added":null,"published":"2021-12-26"},{"cvss_score":9.8,"headline":"Use of Uninitialized Resource in messagepack-rs.","id":"CVE-2021-45692","kev_date_added":null,"published":"2021-12-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":"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-04","vendors":["n/a"]},"summary":"Attackers can trigger uninitialized memory reads in the messagepack-rs Rust crate, potentially exposing sensitive data or causing crashes.","url":"https://insights.sbomify.com/CVE-2021-45693/"}