Fix buggy default in s4u_persistence module #17351
Merged
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
s4u_persistence
module, by default, incorrectly set thefrequency
value, which led to a confusing error message. This fixes that by correctly providing a default in the case of the value beingnil
.Previously, if it was
nil
, this would be treated as "Oh, the user provided a value for us", and this nothingness would be inserted into the XML. Then, you'd receive a failed exploit with the error message:The fix here is just to check for
nil
, and set an appropriate default.Verification
List the steps needed to make sure this thing works
msfconsole
use s4u_persistence
set session <id>
run