-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix java_jmx_server exploit #9413
Conversation
Add test case when discovering RMI endpoint as the previous one was not complete
@tranca, can you provide any more details about the stack you used this against. I don't see much harm in expanding the check, but it would be valuable to have an example environment we can target to test against. Something like OS version, JVM version, and maybe the web server framework used would be enough for us to generate our own vulnerable server. |
It looks like we could just add all of the classes in javax.management.remote.rmi that implement RMIServer. |
@jmartin-r7 I updated my PR with the additional information you requested ! |
Right on @tranca that looks a lot nicer. |
Release NotesThe exploits/multi/misc/java_jmx_server module now works in more environments. |
…king for an exploitable JMX server
…king for an exploitable JMX server
Add test case when discovering RMI endpoint as the previous one was not complete
During a security assessment I encountered a problem with the "java_jmx_server" exploit. After looking at the code I found that the property "javax.management.remote.rmi.RMIServerImpl_Stub" was different than the object that I had: "javax.management.remote.rmi.RMIServer". After adding this test case, the exploit worked.
Here are some additional information about the environment :