updated GetReflectiveLoaderOffset to handle PE32's and PE64's regardless of the injector's architecture #3
Conversation
This file contains hidden or 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
…ess of the injector's architecture
S0PEX
approved these changes
Jun 13, 2017
busterb
added a commit
to busterb/ReflectiveDLLInjection
that referenced
this pull request
Feb 13, 2018
zeroSteiner
pushed a commit
to zeroSteiner/ReflectiveDLLInjection
that referenced
this pull request
May 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I updated GetReflectiveLoaderOffset to handle PE32's and PE64's regardless of the injector's architecture. I did this by adding boolean "is64" parameter to Rva2Offset. If is64 is true, PIMAGE_NT_NEADERS64 is used, otherwise PIMAGE_NT_NEADERS32 is used. This is useful when you have a DLL that doesn't match the architecture of the injecting code.