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 unsafe implementation from Object to T #124

Open
llooFlashooll opened this issue Aug 21, 2024 · 1 comment
Open

Unsound usages of unsafe implementation from Object to T #124

llooFlashooll opened this issue Aug 21, 2024 · 1 comment

Comments

@llooFlashooll
Copy link

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

Unsafe conversion found at: src/runtime.rs#L506

let ptr = {
    let self_ptr: *mut Object = self;
    (self_ptr as *mut u8).offset(offset) as *mut T
};
&mut *ptr

This unsound implementation would create a misalignment issues if the type size of Object is smaller than the type size of T.

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 access out-of-bound. I am reporting this issue for your attention.

@madsmtm
Copy link

madsmtm commented Aug 21, 2024

It is true that Object should ideally be an extern type so that accesses such as this one would be correctly calculated, but extern types are not yet stable in Rust, so instead we use a ZST, which allow some of the same things (for now).

So nothing for objc to do here, Rust needs to progress further with extern types first.

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

2 participants