{"answers":{"affected":"3 open source packages ship an affected version, including arenavec.","exploited":"There is no known exploitation of GHSA-3632-54q8-m96x in the wild and no public exploit code.","fix":"No fix has been published for GHSA-3632-54q8-m96x yet. Limit exposure of the affected software until one is available.","what":"GHSA-3632-54q8-m96x is a memory corruption vulnerability in arenavec, published on 14 Aug 2025."},"fix_prompt":"Check this codebase for GHSA-3632-54q8-m96x and fix it if it is affected.\n\nWhat it is: GHSA-3632-54q8-m96x is a memory corruption vulnerability in arenavec, published on 14 Aug 2025. \nExploitation: There is no known exploitation of GHSA-3632-54q8-m96x in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- arenavec (crates.io): affected all versions up to 0.1.1; no fix listed\n- arenavec (crates.io): affected all versions up to 0.1.1; no fix listed\n- arenavec (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-3632-54q8-m96x/ (Markdown: https://insights.sbomify.com/GHSA-3632-54q8-m96x/index.md)","id":"GHSA-3632-54q8-m96x","markdown":"https://insights.sbomify.com/GHSA-3632-54q8-m96x/index.md","name":"GHSA-3632-54q8-m96x","record":{"aliases":["RUSTSEC-2025-0053"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust memory library","requires_auth":"none","summary":"Memory corruption vulnerabilities in the arenavec Rust crate allow arbitrary memory access, heap overflows, and double frees via safe APIs.","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 crate has the following vulnerabilities:\n\n- The public trait `arenavec::common::AllocHandle` allows the return of raw pointers through its methods `allocate` and `allocate_or_extend`. However, the trait is not marked as unsafe, meaning users of the crate may implement it under the assumption that the library safely handles the returned raw pointers. These raw pointers can later be dereferenced within safe APIs of the crate-such as `arenavec::common::SliceVec::push`-potentially leading to arbitrary memory access.\n\n- The safe API `arenavec::common::SliceVec::reserve` can reach the private function `arenavec::common::allocate_inner`. Incorrect behavior in `allocate_inner` may result in a `SliceVec` with an increased capacity, even though the underlying memory has not actually been expanded. This mismatch between `SliceVec.capacity` and the actual reserved memory can lead to a heap buffer overflow.\n\n- The safe API `arenavec::common::SliceVec::split_off` can duplicate the ownership of the elements in `self` (of type `SliceVec`) if they implement the `Drop` trait. Specifically, when `at == 0`, the method returns a new `SliceVec` with the same length as `self`. Since both `self` and the returned object point to the same heap memory, dropping one will deallocate the shared memory. When the other is subsequently dropped, it will attempt to free the same memory again, resulting in a double free violation.","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 memory corruption vulnerabilities in safe APIs","id":"GHSA-3632-54q8-m96x","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":[],"introduced":["0"],"last_affected":["0.1.1"],"package":"arenavec","purl":null,"source":"GHSA-3632-54q8-m96x"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.1.1"],"package":"arenavec","purl":"pkg:cargo/arenavec","source":"GHSA-3632-54q8-m96x"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"arenavec","purl":"pkg:cargo/arenavec","source":"RUSTSEC-2025-0053"}],"products":null,"published":"2025-08-14","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":"Memory corruption vulnerabilities in the arenavec Rust crate allow arbitrary memory access, heap overflows, and double frees via safe APIs.","url":"https://insights.sbomify.com/GHSA-3632-54q8-m96x/"}