{"answers":{"affected":"3 open source packages ship an affected version, including owning_ref.","exploited":"There is no known exploitation of GHSA-9qxh-258v-666c in the wild and no public exploit code.","fix":"No fix has been published for GHSA-9qxh-258v-666c yet. Limit exposure of the affected software until one is available.","what":"GHSA-9qxh-258v-666c is an use after free vulnerability in owning_ref, published on 26 Jan 2022."},"fix_prompt":"Check this codebase for GHSA-9qxh-258v-666c and fix it if it is affected.\n\nWhat it is: GHSA-9qxh-258v-666c is an use after free vulnerability in owning_ref, published on 26 Jan 2022. \nExploitation: There is no known exploitation of GHSA-9qxh-258v-666c in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- owning_ref (crates.io): affected all versions up to 0.4.1; no fix listed\n- owning_ref (crates.io): affected all versions up to 0.4.1; no fix listed\n- owning_ref (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/GHSA-9qxh-258v-666c/ (Markdown: https://insights.sbomify.com/GHSA-9qxh-258v-666c/index.md)","id":"GHSA-9qxh-258v-666c","markdown":"https://insights.sbomify.com/GHSA-9qxh-258v-666c/index.md","name":"GHSA-9qxh-258v-666c","record":{"aliases":["RUSTSEC-2022-0040"],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust owning_ref crate","requires_auth":"none","summary":"Unsound APIs in the owning_ref crate allow use-after-free vulnerabilities, potentially leading to code execution or crashes; users should migrate to safer_owning_ref.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"- `OwningRef::map_with_owner` is [unsound](https://github.com/Kimundi/owning-ref-rs/issues/77) and may result in a use-after-free.\n- `OwningRef::map` is [unsound](https://github.com/Kimundi/owning-ref-rs/issues/71) and may result in a use-after-free.\n- `OwningRefMut::as_owner` and `OwningRefMut::as_owner_mut` are [unsound](https://github.com/Kimundi/owning-ref-rs/issues/61) and may result in a use-after-free.\n- The crate [violates Rust's aliasing rules](https://github.com/Kimundi/owning-ref-rs/issues/49), which may cause miscompilations on recent compilers that emit the LLVM `noalias` attribute.\n\n`safer_owning_ref` is a replacement crate which fixes these issues.\nNo patched versions of the original crate are available, and the maintainer is unresponsive.","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":false,"headline":"Multiple soundness issues in `owning_ref`","id":"GHSA-9qxh-258v-666c","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2022"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.4.1"],"package":"owning_ref","purl":null,"source":"GHSA-9qxh-258v-666c"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.4.1"],"package":"owning_ref","purl":"pkg:cargo/owning_ref","source":"GHSA-9qxh-258v-666c"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"owning_ref","purl":"pkg:cargo/owning_ref","source":"RUSTSEC-2022-0040"}],"products":null,"published":"2022-01-26","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":"Unsound APIs in the owning_ref crate allow use-after-free vulnerabilities, potentially leading to code execution or crashes; users should migrate to safer_owning_ref.","url":"https://insights.sbomify.com/GHSA-9qxh-258v-666c/"}