Added Timestamps to JRMPListener exploit output #101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have found that when using JRMPListener, there is sometimes a delay between when the vulnerable system receives a payload and when the vulnerable system contacts the JRMPListener listener. It is also normal for the vulnerable system to contact the JRMPListener multiple times after receiving a single payload. Because of these factors, it can be beneficial to know exactly when contact was made between the vulnerable system and the JRMPListener.
The current output from JRMPListener does not contain any timestamps. I have added date (MM/DD/YYYY) and time (HH:MM:SS) timestamps to the ysoserial.exploit.JRMPListener class like so: "11/03/2018 21:39:44: Have connection from /192.168.0.18:25307"