Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsound usages of VecFromRawParts #108

Open
llooFlashooll opened this issue Aug 20, 2024 · 0 comments
Open

Unsound usages of VecFromRawParts #108

llooFlashooll opened this issue Aug 20, 2024 · 0 comments

Comments

@llooFlashooll
Copy link

Hi, I am scanning the scavenger in the latest version with my own static analyzer tool.

Unsafe conversion found at: src/miner.rs#L141

pub fn new(buffer_size: usize) -> Self {
    let pointer = aligned_alloc::aligned_alloc(buffer_size, page_size::get());
    let data: Vec<u8>;
    unsafe {
        data = Vec::from_raw_parts(pointer as *mut u8, buffer_size, buffer_size);
    }

This unsound implementation of Vec::from_raw_parts would create a dangling pointer issues if the pointer is dropped automatically or is empty. The 'mem::forget' function can be used to avoid the issue.

This would potentially cause undefined behaviors in Rust. If we further manipulate the problematic converted types, it would potentially lead to different consequences such as uaf or double free. I am reporting this issue for your attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant