[peview] Add safeguards around using loadconfig most recent members #123
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.
Since the last PR on
CFG
tab forpeview
(#101), I've noticed somePE
has aGuardFunctionTable
but does not define aGuardAddressTakenIatEntryTable
or aGuardLongJumpTargetTable
(mainlyWow64
ones).This PR add safeguards when parsing the load configuration, in order to read only what's defined and no more. This is basically the
NT
loader 's parsing algorithm for load configurations.