Draft
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
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.
Motivation for change
Upgrading to volatility3 after PANDA upgrade
Additional information
For reference, this is the old code for svcscan:
volatility3 has decoupled the
DriverNamefield from svcscan nodes.To parse the plugin output, you need to walk the treegrid using a visitor function as so:
The reason for these 4 functions is that when you run
svcscan, the nodes in the treegrid contain abinaryandbinary_registryfield:However, those are not what we want. We need the actual name of the driver which we can get from the
driverscanplugin node's 'name' field.This forces us to have to run
driverscanfirst and then iterate through the services and match them.The problem with this code is that the driver offsets do not match with those of the service, so you cannot match the driver names properly.
The other approach is as follows:
Find one of the drivers by running
get_driverscan()function and its offsetFind the symbol tables in the symbol space
symbol_table_name1has the kernel symbolsNext list the symbols
I ommited the output because it's very large but the one we're looking for is
'_DRIVER_OBJECT'Get the driver object
Attempt to get the driver name
DriverNameis aUNICODE_STRINGas shown here: https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/ns-wdm-_driver_objectI'm not even able to read the length of
DriverNameso that I can read the raw bytes