Port 1099RMI Registry
RMI Registry is a service used by Java applications to register and look up remote objects within distributed computing environments. It facilitates communication between Java-based client and server applications, enabling seamless invocation of methods across network boundaries..
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 5,946
2 transports registered
payload readable on path
registered with iana
caution
rank 834 of 993 · top 84%
Technical Details
what runs on :1099Overview:
The RMI Registry, running by default on port 1099, is a core component of Java’s Remote Method Invocation (RMI) framework. It serves as a simple name service allowing Java objects to be registered and subsequently looked up across a distributed system. Developers make use of it to locate stubs for remote objects so that method invocations can occur transparently over the network.
How it Works:
The RMI Registry uses a straightforward key-value store approach—remote objects are associated with unique textual names and then bound to the registry. Clients query the registry for these names, receive a stub (proxy object) in return, and then invoke the remote object’s methods as if they were local, with the RMI system handling network communication, marshalling, and unmarshalling behind the scenes.
Protocols and Use Cases:
Port 1099 supports both TCP and UDP protocols, though communication primarily occurs over TCP for reliability. RMI Registry is widely used within Java Enterprise environments, distributed middleware systems, and in legacy enterprise applications that depend on Java EE technologies, especially before the rise of modern microservices and RESTful APIs.
Security Information
exposure of :1099risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
network services averages 3.9 across 604 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
official
registered with iana for this service — scanners fingerprint it by number
reachable over
tcp · udp
udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite
security overview
Common Vulnerabilities:
- Unauthorized remote access: Without proper access controls, attackers can query the registry, discovering or binding malicious objects.
- RMI Deserialization attacks: Vulnerabilities in Java serialization can be exploited to execute arbitrary code during deserialization.
- Man-in-the-middle attacks: Since data is often transmitted unencrypted, it can be intercepted or modified.
Common Mitigations:
- Access Controls: Restrict who can connect to the RMI Registry using network filters and Java Security Manager policies.
- Encryption: Wrap RMI communication in SSL/TLS using Java’s SSL RMI Socket Factories.
- Authentication: Implement client and server authentication to prevent unauthorized access.
- Network Segmentation: Keep RMI Registry behind firewalls and expose it only within internal networks.
- Patch regularly: Keep the Java runtime updated to mitigate known deserialization vulnerabilities.
Related Ports
the 8 most looked-up other ports in network services — 604 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :6543 | Jetnet | UDP | Network Services | caution | 65.3k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3233 | WhiskerControl Protocol | TCPUDP | Network Services | caution | 61.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Tatsoft Default HTTP Proxy | TCP | Web Services | caution | 46.8k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted