# WHATPORT(1050)

## NAME

port 1050 — CORBA Management Agent / J2EE naming — Registered as CORBA Management Agent; in practice Nmap fingerprints TCP 1050 as a J2EE nameserver.

Protocol: TCP  
IANA registry

## DESCRIPTION

IANA registers 1050 as "cma — CORBA Management Agent", a vendor registration from the CORBA era. Nmap's own service table disagrees about what actually shows up: it labels TCP 1050 `java-or-OTGfileshare`, noting a J2EE nameserver and OTG's Disk/Application Extender as the common occupants, and keeps `cma` only on the UDP side. Either way you are looking at an object-broker or naming service, which is a remote-object endpoint rather than an application protocol. Naming and object-lookup services of this generation typically hand out object references and deserialize what clients send them, which is why they attract attention.

## EXPOSURE

**Do not expose.** Object brokers and Java naming services generally accept unauthenticated lookups and deserialize client data — a well-worn remote-code-execution path. Bind it to an internal interface only.

## CHECK

```sh
nmap -Pn -sV --script giop-info -p 1050 TARGET
```

## SEE ALSO

- iana — [IANA Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) (iana.org)
- docs — [Nmap giop-info NSE script (CORBA/GIOP naming service query)](https://nmap.org/nsedoc/scripts/giop-info.html) (nmap.org)
- docs — [Nmap service frequency database (nmap-services)](https://svn.nmap.org/nmap/nmap-services) (svn.nmap.org)

---

HTML: <https://whatport.net/1050/> · JSON: <https://whatport.net/1050.json> · full dataset: <https://whatport.net/ports.json>