Port 4750BladeLogic Agent
**BladeLogic Agent** facilitates communication between BMC's BladeLogic Server Automation platform and managed servers. It enables administrators to automate configuration, provision systems, manage software deployment, and monitor server compliance via a secure agent running on the target device..
- transport
- tcp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 8,679
single transport
payload readable on path
used by convention
caution
rank 583 of 993 · top 59%
Technical Details
what runs on :4750BladeLogic Agent is an endpoint component of BMC's BladeLogic Server Automation suite. It provides a secured communication channel for executing administrative commands remotely and managing server lifecycles. Typically installed as a system service, the agent listens on TCP port 4750 to receive instructions from the BladeLogic Application Server (AppServer).
The agent supports various operations like patch management, inventory collection, compliance assessments, and software deployments. It leverages role-based access control and integrates with enterprise identity management solutions for secure operation. Communication is initiated by authenticated AppServers that issue commands which the agent executes locally, ensuring operations adhere to established policies.
BladeLogic Agent is a core part of enterprise infrastructure automation, scaling global server management through reliable connectivity. It requires consistent network availability and appropriate firewall configuration, with port 4750 needing to be open between management servers and endpoints.
Security Information
exposure of :4750risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
network services averages 3.9 across 604 ports — this one sits 0.1 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities:
- Unauthorized access due to weak or default credentials
- Exploitation of unpatched vulnerabilities in outdated agent versions
- Man-in-the-middle (MitM) attacks if data transmission lacks sufficient encryption
- Misconfigurations that expose management interfaces to untrusted networks
Common Mitigations:
- Employ strong, unique authentication credentials with role-based permissions
- Regularly update the agent to the latest secure release
- Restrict port 4750 access to trusted management servers via firewalls
- Use network encryption (e.g., TLS) if supported to protect data in transit
- Monitor and log agent communication for anomalous activity to detect compromise attempts
Related Ports
the 8 most looked-up other ports in network services — 604 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :6543 | Jetnet | UDP | Network Services | caution | 65.3k |
| :5938 | TeamViewer | TCPUDP | Remote Access | caution | 65.0k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3233 | WhiskerControl Protocol | TCPUDP | Network Services | caution | 61.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Tatsoft Default HTTP Proxy | TCP | Web Services | caution | 46.8k |
risk mix of the 8 listed
- caution100%
0 of 8 encrypted