Registered · Cross-platform

1099 Java RMI registry

TCP Yes
UDP Assigned
SCTP
DCCP

What it is

Java RMI registry.

When / why

Java remote objects. Deserialization RCE risk — never internet-exposed.

Protocol status detail

TransportStatusMeaning
TCP Yes Assigned by IANA and standardized, specified, or widely used on this port.
UDP Assigned Assigned by IANA, but not standardized, specified, or widely used on this port.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 1099

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

⚠ High exposure risk — this service should never be reachable from untrusted networks. Scope the rule to a management subnet or VPN.

ufw

sudo ufw allow proto tcp from <source> to any port 1099

Allow TCP 1099 (Java RMI registry). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="1099" protocol="tcp" accept'

Allow TCP 1099 (Java RMI registry) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 1099 accept

Allow TCP 1099 (Java RMI registry). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 1099 -j ACCEPT

Allow TCP 1099 (Java RMI registry). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-javarmiregistry-1099 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 1099

Inbound rule for 1099 (Java RMI registry). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=1099,ToPort=1099,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 1099 (Java RMI registry). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-javarmiregistry-1099 --direction=INGRESS --action=ALLOW --rules=tcp:1099 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 1099 (Java RMI registry). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Java RMI registry 1099/TCP" dir=in action=allow protocol=TCP localport=1099 remoteip=<source>

Inbound TCP 1099 (Java RMI registry). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Java RMI registry 1099/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 1099 -RemoteAddress <source>

Inbound TCP 1099 (Java RMI registry). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.