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
64 bit compatibility #2
Comments
Hi, As indicated in the readme, I tested this PoC on Windows 10 64 bits - can you provide your OS and office version? Thanks |
I am trying it on Windows 10 and Office 365 MSO (16.0) 64-bit. |
+1 This doesn't work with 64-bit Office. The typedefs need modifying and I also don't think the getPidByName() function words for 64-bit processes. The latter I can get around with WMIC but I'm unsure how to modify the typedefs or function declarations for 64-bit. Niiiice work on the 32-bit though. |
Hi, Thanks for the update. I double checked, and indeed the Office version I own is a 32-bit version... Apologies for the confusion. I have updated the README to reflect this. If someone could contribute to a 64-bit version, that'd be awesome - I do not have access to a 64-bit Office version at the time. |
Looking for any progress by anyone on this. Personally I've got to the point where the parent PID spoofing on x64 works, but the argument spoofing does not. There are no errors from any of the API calls, and I believe the issue is currently with the call to WriteProcessMemory(), but I don't know how to debug further. |
What I would suggest to do is:
|
@christophetd I submitted a pull request yesterday for the 64 bit implementation. Tested it with Office 365 (2016) 64-bit on 64 bit system. Learnt a lot while doing this. |
Merged! (#5) |
Hey I am trying to use the VB macro on 64-bit machine O365 but looks like it's not compatible. It gave some ptrsafe errors. I fixed them by adding ptrsafe to the declare statements but then I got some ByRef errors. I also tried converting long to longptr as suggested in some articles for converting 32 nit vb to 64 bit. Is there any chance that you can provide 64 bit version or any tips to fix the errors?
The text was updated successfully, but these errors were encountered: