Confusion between java-rmi and rmiregistry

Bastien Faure via dev <[email protected]> Fri, 5 Oct 2018 09:04:43 +0000
Newsgroups gmane.comp.security.nmap.devel
Message-ID <[email protected]>
Hi there,

I always wondered about how Java and RMI services worked. Since I got a 
little bit more interested in them, I noticed that there might be a 
confusion on nmap side about the service naming. Let's take an example:

PORT     STATE SERVICE     VERSION
9000/tcp open  rmiregistry Java RMI
9001/tcp open  java-rmi    Java RMI Registry
| rmi-dumpregistry:
|   jmxrmi
|     javax.management.remote.rmi.RMIServerImpl_Stub
|     @172.16.1.103:9000
|     extends
|       java.rmi.server.RemoteStub
|       extends
|_        java.rmi.server.RemoteObject

Port 9001 is a port that I configured as the registry, which is the 
place where remote users can find stubs to retrieve. Here my registry 
only contains one stub at port 9000.

So basically, may the service names be reversed ? For me the rmiregistry 
should be at port 9001, not the opposite. Also, the rmi-dumpregistry 
script was run on java-rmi, which comfort my position :D

Do you agree with that ?

Thanks !

-- 

Bastien Faure

*Security Associate*

(602) 570-6027

_www.bishopfox.com_ <http://www.bishopfox.com/>

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/
smime.p7s (application/pkcs7-signature, 3.9 KB) - not displayed