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

Is there requirement of bruteforcing the address for 64 bit? #1

Open
jai-the-seeker opened this issue May 25, 2020 · 0 comments
Open

Comments

@jai-the-seeker
Copy link

It is understandable that for 64 bit, virtualAlloc function we have used address spaces greater than 32 bit to avoid truncation bug. However, we could pick any random address space greater than 32 bit, instead of bruteforcing. In case, the address space is already reserved and committed, the address will be rounded down to next page boundary. In this regard please refer to Microsoft documentation.

https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-virtualalloc

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