NetSight
medium5.5No CVE yet

GHSA-77h3-w9rx-hj3q

User-defined implementations of the safe trait scratchpad::Tracking can cause heap buffer overflows

Impact

The `get` and `set` methods of the public trait `scratchpad::Tracking` interact with unsafe code regions in the crate, and they influence the computation of addresses returned as raw pointers. However, the trait itself is not marked as unsafe, meaning users may provide custom implementations under the assumption that the crate upholds all safety guarantees. This becomes problematic because even safe implementations of `get` and `set`-written without using any unsafe code-can still result in ill-formed raw pointers. These pointers may later be dereferenced within safe APIs of the crate (e.g., `marker::MarkerBack::allocate_slice_copy`), potentially leading to arbitrary memory access or heap buffer overflows. According to the [penultimate commit](https://github.com/okready/scratchpad/commit/957dee1a3902f48600b06910e8e0b1d5ee7dab83), the crate is in maintenance mode awaiting a cleanup that will reduce the area of unsafe code. Note that the last commits to the repository are from 4 years ago.

An attacker can exploit this with local access to the system, without logging in, without any action by a user. If it succeeds: high risk of outages.

Affected packages

EcosystemPackageAffectedFixed in
rustscratchpad<= 1.3.1none recorded

Weakness classification

References