Описание
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.
Пакеты
arenavec
<= 0.1.1
Отсутствует
8.9 High
CVSS4
Дефекты
8.9 High
CVSS4