Closed gleeda closed 6 years ago
I'm having difficulty recreating this. Is the image you're using available for testing (can you put them on the volatility test boxes?). I've been through 3 or 4 different images and none of them appear to have self-referential keys under ControlSet001\Control\Arbiters
. I've been using the system hive, unless it's under a different hive?
It was from the system hive from this memory sample:
http://buildbot.volatilityfoundation.org/volatility3/images/download/
This should be resolved now. I extended the get_key
method to return a node list, and if we've ever seen it in that list we don't traverse it again (basic loop avoidance). It might add a memory hit and potential speed hit for very deep or broad key recursion (such as classes or something very far down the tree), but we'll need to experiment to see how bad that is...
Something, is broken in the way that we are recursing registry keys. I'm not sure if it's the recursion itself, or just the way the registry key path is appended just yet. For example:
I remember hitting something similar to this with vol2. In that case it was because we were blindly following pointers, and sometimes they are corrupt and might be circular.