Port 13076BMC Control-M CORBA Connection
Port 13076 is typically used as the default communication endpoint for BMC Software's Control-M/Enterprise Manager which leverages CORBA technology for inter-component messaging and orchestration. This port facilitates the coordination of scheduling services, though it is often altered during installation to comply with existing network policies or to improve security posture..
- transport
- tcp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 14,803
single transport
payload readable on path
registered with iana
caution
rank 225 of 993 · top 23%
Technical Details
what runs on :13076Port 13076 is designated by BMC Software for the CORBA-based communication subsystem within the Control-M/Enterprise Manager suite. CORBA (Common Object Request Broker Architecture) allows distributed objects to interoperate across networked environments, enabling seamless interaction between diverse components managing batch workflow and job scheduling.
By utilizing CORBA middleware, Control-M integrates heterogeneous systems, databases, and applications to orchestrate complex workflows efficiently. The port manages messaging and command transmission essential for job execution, monitoring, and system state synchronization. Since BMC often allows this port to be customized during deployment, administrators might change it to avoid conflicts or improve segregation within network firewalls.
Despite its proprietary context, this port enables connectivity between the Enterprise Manager console, agents, and various Control-M modules. The communication on this port underpins many enterprise-level automation features, ensuring timely job initiation, tracking, and resource management.
Security Information
exposure of :13076risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
system averages 3.9 across 342 ports — this one sits 0.1 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
every listening transport is another surface to filter at the edge
security overview
Common vulnerabilities associated with port 13076 stem largely from exposed CORBA services which may include:
- Exposure to unauthorized remote access if the Control-M scheduler interfaces are left unprotected.
- Susceptibility to replay attacks, man-in-the-middle interception, or command injection, especially if default configurations are used.
- Information leakage due to verbose CORBA messaging, which may assist attackers in fingerprinting enterprise architecture.
Mitigations include:
- Ensuring the port is firewalled from untrusted networks, allowing only authorized management hosts.
- Implementing authentication and access controls within the Control-M environment.
- Disabling or encrypting CORBA communication where possible.
- Regularly updating BMC software to patch potential vulnerabilities.
- Changing the default port during setup to minimize common exploit attempts.
Related Ports
the 8 most looked-up other ports in system — 342 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8888 | Sun Answerbook & Alt HTTP | TCP | Web Services | caution | 123.9k |
| :4664 | Google Desktop Search | TCP | System | caution | 67.2k |
| :8008 | IBM HTTP Server Admin | TCP | Web Services | caution | 58.3k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :9080 | WebSphere HTTP Transport (default) | TCP | Web Services | caution | 51.6k |
| :23 | Telnet | TCP | Remote Access | caution | 34.8k |
| :12489 | NSClient Monitoring Agent | TCP | Network Services | caution | 30.0k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted