{
  "port": 1050,
  "protocol": "tcp",
  "service": "CORBA Management Agent / J2EE naming",
  "oneLiner": "Registered as CORBA Management Agent; in practice Nmap fingerprints TCP 1050 as a J2EE nameserver.",
  "whatItIs": "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": {
    "verdict": "never",
    "note": "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."
  },
  "checkCommand": "nmap -Pn -sV --script giop-info -p 1050 TARGET",
  "links": [
    {
      "title": "IANA Service Name and Transport Protocol Port Number Registry",
      "url": "https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml",
      "kind": "iana"
    },
    {
      "title": "Nmap giop-info NSE script (CORBA/GIOP naming service query)",
      "url": "https://nmap.org/nsedoc/scripts/giop-info.html",
      "kind": "official-docs"
    },
    {
      "title": "Nmap service frequency database (nmap-services)",
      "url": "https://svn.nmap.org/nmap/nmap-services",
      "kind": "official-docs"
    }
  ]
}