Port 2482: Oracle GIOP SSL — The Encrypted Voice of CORBA

What This Port Does

Port 2482 is the SSL-encrypted channel for Oracle's implementation of GIOP — the General Inter-ORB Protocol. It works as a pair with port 2481: cleartext GIOP on 2481, encrypted GIOP on 2482.

When Oracle databases needed to serve CORBA objects or EJB components to remote clients, connections arrived on one of these two ports depending on whether SSL was required. Port 2482 is the answer to "same thing, but encrypted."

What GIOP Actually Is

GIOP is the message protocol that makes CORBA work. CORBA — the Common Object Request Broker Architecture — was the late 1990s answer to a real problem: how do you let a Java program on one machine call a method on a C++ object running on a different machine, transparently, as if they were in the same process?

GIOP is the protocol that carries those remote method calls. IIOP (Internet Inter-ORB Protocol) is GIOP running over TCP/IP — the specific flavor that made CORBA usable across the Internet. SSLIOP is IIOP over SSL, which is what you're looking at on port 2482.¹

Oracle baked CORBA support directly into its database product in the early 2000s, letting clients access EJB beans and CORBA objects stored or proxied through the database engine. Port 2481 handled the plain connections; port 2482 handled the encrypted ones.²

What Happened to It

CORBA was supposed to be the universal distributed computing standard. Every major vendor implemented it. The OMG (Object Management Group) published careful specifications. And then REST happened, and XML-RPC, and later JSON APIs — simpler protocols that didn't require an ORB on both ends.

CORBA didn't disappear entirely. It still runs in telecom, defense, and industrial systems where the investment in OMG-compliant infrastructure was too deep to abandon. But for most Oracle deployments today, port 2482 sits quiet. The architecture it served has largely been replaced by JDBC connections and RESTful APIs.

Security Considerations

Port 2482 carries SSL, so the traffic itself is encrypted. But CORBA infrastructure has a history of complex security models that were easy to misconfigure. If you see unexpected traffic on this port, it warrants investigation — CORBA endpoints that aren't deliberately exposed should be firewalled.

The more common finding: port 2482 open on a database server that hasn't used CORBA in years, because nobody remembered to close it.

How to Check What's Listening

# Linux/macOS
ss -tlnp | grep 2482
lsof -i :2482

# Windows
netstat -ano | findstr :2482

If Oracle is installed and the listener is configured for IIOP, you may see tnslsnr (the Oracle TNS Listener process) holding this port.

Related Ports