Port 2809CORBA Naming Service

CORBA Naming Service and IIOP object references commonly use port 2809.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
6/10

risk

lookups
0

rank 994 of 1,815 · top 55%

also known as corbaloc, IIOP, GIOP

2 other services are registered on port 2809. compare all 3

Technical Details

what runs on :2809

CORBA clients normally communicate with the Naming Service using IIOP, the Internet Inter-ORB Protocol, over TCP. IIOP carries GIOP messages using binary CDR encoding, including requests to resolve names and return interoperable object references; the service commonly listens on TCP 2809. The registry also lists UDP, but ordinary CORBA Naming Service deployments use TCP rather than UDP. TLS-capable variants such as SSLIOP exist, but are not enabled by default.

Security Information

exposure of :2809

risk score

6/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

network services averages 3.3 across 815 ports — this one sits 2.7 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

Traffic is unencrypted by default, and an exposed Naming Service may disclose object references or permit access to remotely invocable CORBA objects, depending on the server's authentication and authorization controls. It should normally be restricted to trusted application networks and monitored for vulnerable or unauthenticated CORBA implementations rather than exposed to the public internet.

the 8 most looked-up other ports in network services — 815 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted