Registered as CORBA Management Agent; in practice Nmap fingerprints TCP 1050 as a J2EE nameserver.
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.
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.
$ nmap -Pn -sV --script giop-info -p 1050 TARGETSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.