-
Notifications
You must be signed in to change notification settings - Fork 812
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
Macro compatibility #158
Comments
This is what microsoft said And it is hard to know whether our pentesting goal is running on x64 or x86 office,so unicorn must be compatible for them all😃 |
I have done some research. That is what i want to say. |
Hi @trustedsec
Which version of office you used to create the payload?
office 2003,2007,2010,2013...... which one?
I am certain that the macro created in newer version(2016,2019...) may not run well on older version(2007,2010...)
And what's the environment of your ms office?
is x86 office or x64 office?
I said that because there is a incompatibilty between x86 office and x64 office,some vba script for x86 cannot run well on x64 office,like invoking some win32 api.
And that is why microsoft recommended that we should use x86 office for less error.
That is,if unicorn is written for x86 office,it is possible that the code generated by unicorn may occur an error on x64 office.
I hope that i could hear your suggestion about the "best" version of office to create the payload!!!
Thank you~
The text was updated successfully, but these errors were encountered: