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
NULL PTR Issue (Bit Strange Windows 7) #11
Comments
Hi, thanks for posting! Sorry you're having trouble. Can you please post the command line output? |
Result of just running Gargoyle.exe.
First execution runs the messagebox, awesome. I click the two initial ones that pop after immediate execution. APC is queued, 15 seconds later, the APC executes and checking with a debugger for the crash shows its jumping to NULL (bit weird) |
Hmm, it's not immediately obvious to me what's wrong. Your version of mshtml.dll doesn't have the correct ROP gadget, but this shouldn't matter since it's creating one for you. Could you attach a debugger and step through the assembly? You'll want to see where the APC callback is, put a breakpoint there, then pay attention to what's happening when the ROP gadget redirects execution (it should point to VirtualProtectEx). |
Nada. Debugged, the APC callback wasnt null which was strange. yeah looks like the issue is with the stack pivot @JLospinoso |
Eh, weird. Since I can't reproduce it, it's hard for me to say much else about what could be wrong. I'll keep the issue open, please let me know if you figure out what's going on! |
Hello! Was hoping you'd have an idea to this
Your project is awesome btw, so I thought I'd try to use it in my own. However, one issue occurs on Windows 7 (x64). When running gargoyle.exe, itll pop the two messagebox's (the initial two) then immediate after the APC is queued, hop to a NULL address. This issue does not appear on any operating system. I tried debugging myself/finding the issue but unable to find it/fix it, so wanted to ask if you have an idea of how one could fix it?
Anyhow, I appreciate you're response, & thank you!
The text was updated successfully, but these errors were encountered: