ms14_012_cmarkup_uaf : Be sure which the full payload is used #3642
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.
Has been reported by Hyunjun Kim from FireEye which ms14_012_cmarkup_uaf was failing with meterpreter/reverse_http. Indeed the fault wasn't meterpreter/reverse_http, but the exploit not using the full payload unless the payload's length is multiple of 4. Since the payload length is LHOST IP length dependent, it was failing when using some LHOSTs.
The exploit now should work with windows/meterpreter/reverse_http (with the same ratio success than other payloads of course :)) , no matters what is the length of the LHOST IP: