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

frida-windows: Hook file memory mapping/unmapping functions to correctly poison/unpoison memory #2225

Open
s1341 opened this issue May 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@s1341
Copy link
Collaborator

s1341 commented May 20, 2024

frida-asan assumes all correctly addressable memory is unpoisoned, and all invalid memory is poisoned.

In order to maintain this invariant, we need to make sure that when files are mapped into memory, they are unpoisoned, and when they are unmapped, they are poisoned. We already hook MapViewOfFile, but need to hook any other similar functions, as well as the unmapping functions.

@s1341 s1341 added the enhancement New feature or request label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant