Fix ScanForModules_MemoryWalk_Hidden and add new .NET structure scan. #238
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
The memory walk check was broken because it assumed that memory regions would be executable. It also started at the wrong address - AllocationBase is the start of the allocator region, whereas BaseAddress is the actual start of the region. This has now been fixed. This commit also adds a new check, which scans for memory structures that the .NET runtime creates to track loaded modules. This should catch injected modules even if they're dynamically loaded from memory.
ayoubfaouzi
approved these changes
Jun 13, 2021
| { | ||
| auto moduleData = static_cast<PBYTE>(region->AllocationBase); |
| @@ -408,6 +410,90 @@ BOOL ScanForModules_MemoryWalk_Hidden() | |||
| return anyBadLibs ? TRUE : FALSE; | |||
| } | |||
|
|
|||
| BOOL ScanForModules_DotNetModuleStructures() | |||
fengjixuchui
added a commit
to fengjixuchui/al-khaser
that referenced
this pull request
Jun 16, 2021
Merge pull request ayoubfaouzi#238 from LordNoteworthy/scan_for_mo…
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.
The memory walk check was broken because it assumed that memory regions would be executable. It also started at the wrong address - AllocationBase is the start of the allocator region, whereas BaseAddress is the actual start of the region. This has now been fixed.
This commit also adds a new check, which scans for memory structures that the .NET runtime creates to track loaded modules. This should catch injected modules even if they're dynamically loaded from memory.
This fixes #234 and #237.