{"answers":{"affected":"3 open source packages ship an affected version, including borrowck_sacrifices.","exploited":"There is no known exploitation of GHSA-xcpm-76hf-c9cc in the wild and no public exploit code.","fix":"Upgrade borrowck_sacrifices to 0.2.0 or later.","what":"GHSA-xcpm-76hf-c9cc is a memory corruption vulnerability in borrowck_sacrifices, published on 21 Oct 2025."},"fix_prompt":"Check this codebase for GHSA-xcpm-76hf-c9cc and fix it if it is affected.\n\nWhat it is: GHSA-xcpm-76hf-c9cc is a memory corruption vulnerability in borrowck_sacrifices, published on 21 Oct 2025. \nExploitation: There is no known exploitation of GHSA-xcpm-76hf-c9cc in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- borrowck_sacrifices (crates.io): affected all versions; fixed in 0.2.0\n- borrowck_sacrifices (crates.io): affected all versions; fixed in 0.2.0\n- borrowck_sacrifices (crates.io): affected from 0.0.0-0; fixed in 0.2.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/GHSA-xcpm-76hf-c9cc/ (Markdown: https://insights.sbomify.com/GHSA-xcpm-76hf-c9cc/index.md)","id":"GHSA-xcpm-76hf-c9cc","markdown":"https://insights.sbomify.com/GHSA-xcpm-76hf-c9cc/index.md","name":"GHSA-xcpm-76hf-c9cc","record":{"aliases":["RUSTSEC-2025-0107"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust memory utility","requires_auth":"none","summary":"A Rust library function exposes uninitialized memory via unsafe slice creation, potentially leading to undefined behavior and information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The safe function `any_as_u8_slice` can create byte slices that reference uninitialized memory when used with types containing padding bytes.\n\nThe function uses `slice::from_raw_parts` to create a `\u0026[u8]` covering the entire size of a type, including padding bytes. According to Rust's documentation, `from_raw_parts` requires all bytes to be properly initialized, but padding bytes in structs are not guaranteed to be initialized. This violates the safety contract and causes undefined behavior.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Borrowck Scarifices exposes uninitialized memory in any_as_u8_slice","id":"GHSA-xcpm-76hf-c9cc","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"borrowck_sacrifices","purl":null,"source":"GHSA-xcpm-76hf-c9cc"},{"ecosystem":"crates.io","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"borrowck_sacrifices","purl":"pkg:cargo/borrowck_sacrifices","source":"GHSA-xcpm-76hf-c9cc"},{"ecosystem":"crates.io","fixed":["0.2.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"borrowck_sacrifices","purl":"pkg:cargo/borrowck_sacrifices","source":"RUSTSEC-2025-0107"}],"products":null,"published":"2025-10-21","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A Rust library function exposes uninitialized memory via unsafe slice creation, potentially leading to undefined behavior and information disclosure.","url":"https://insights.sbomify.com/GHSA-xcpm-76hf-c9cc/"}