Summary
arenavec has multiple memory corruption vulnerabilities in safe APIs
The crate has the following vulnerabilities:
The public trait
arenavec::common::AllocHandleallows the return of raw pointers through its methodsallocateandallocate_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 asarenavec::common::SliceVec::push-potentially leading to arbitrary memory access.The safe API
arenavec::common::SliceVec::reservecan reach the private functionarenavec::common::allocate_inner. Incorrect behavior inallocate_innermay result in aSliceVecwith an increased capacity, even though the underlying memory has not actually been expanded. This mismatch betweenSliceVec.capacityand the actual reserved memory can lead to a heap buffer overflow.The safe API
arenavec::common::SliceVec::split_offcan duplicate the ownership of the elements inself(of typeSliceVec) if they implement theDroptrait. Specifically, whenat == 0, the method returns a newSliceVecwith the same length asself. Since bothselfand 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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-3632-54Q8-M96X? GHSA-3632-54Q8-M96X is a high-severity security vulnerability in arenavec (rust), affecting versions <= 0.1.1. No fixed version is listed yet.
- Which versions of arenavec are affected by GHSA-3632-54Q8-M96X? arenavec (rust) versions <= 0.1.1 is affected.
- Is there a fix for GHSA-3632-54Q8-M96X? No fixed version is listed for GHSA-3632-54Q8-M96X yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-3632-54Q8-M96X exploitable, and should I be worried? Whether GHSA-3632-54Q8-M96X is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-3632-54Q8-M96X is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.