Fix undeclared next_section_virtual_address usage #429
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 following two files are making pefile crash with the next stacktrace:
aksdf.sys
hardlock.sys
From my understanding, the
parse_sections
function may end up callingself.is_driver()
as it's parsing the sections, but before theparse_sections
function goes over the newly parsed sections to configure thenext_section_virtual_address
variable. Sinceis_driver()
ends up relying on it, it is crashing.I believe the code that needs the
is_driver()
call is only adding warnings, so it would not cause any functional change to put it after the code assigning the value tonext_section_virtual_address
.