Java JMX Package Name Randomization #9896
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.
This change randomizes the MBean package name inside the jar.
This achieves two goals:
A. Most importantly, this allows multiple session from the same exploit to work at once. This is needed if the attacker's IP has changed or there is a collaborator attempting to get a shell.
Previously, without package name randomization, the exploit would fail because the IP address is packaged within the JAR and once loaded by the JVM, would not be reloaded again since a package+ class combo is already loaded.
B. This allows the payload to be a little more stealthy and not stand out like a sore thumb in the process logs.