Update IE unsafe scripting module #2299
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Note: Travis CI error doesn't look related to the module. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This module removes the requirement for ADODB.Stream which is blocked by default even when unsafe scripting methods are allowed. Instead we just use the VBS to write the EXE for us (we use to create a VBS file anyway).
Have also added a technique to take advantage of Powershell to avoid dropping a file to the disk at all. Strangely even when IE is run in x64 mode, all tabs are x86 and WScript.Shell and Powershell are therefore SYSWOW64. We cant run x64 payloads in these Powershell instances but luckily this saves the user from having to guess (or recon) the correct architecture!