Port 10010ooRexx rxapi daemon
The Open Object Rexx (ooRexx) rxapi daemon provides network-based API services that enable external applications to interface programmatically with the ooRexx interpreter, allowing for automation, scripting integration, and remote management capabilities..
- transport
- tcp
- in transit
- cleartext
- assignment
- official
- risk
- 4/10
- lookups
- 9,198
single transport
payload readable on path
registered with iana
caution
rank 526 of 993 · top 53%
Technical Details
what runs on :10010Open Object Rexx (ooRexx) is an object-oriented scripting language descended from IBM Rexx, used primarily to streamline automation and integrate legacy Rexx scripts with modern systems.
The rxapi daemon listens on port 10010/TCP and acts as a network-accessible API gateway. It allows external processes or applications to interact with the ooRexx interpreter remotely, granting capabilities such as invoking scripts, querying script status, and managing execution contexts across distributed environments.
rxapi supports various request types and typically communicates over simple socket connections. The daemon extends ooRexx’s integration capabilities beyond local execution, facilitating distributed scripting automation and streamlined development workflows across networked systems.
Security Information
exposure of :10010risk 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
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 the ooRexx rxapi daemon include:
- Unauthorized Access: Without proper authentication, malicious users may execute arbitrary scripts remotely, potentially compromising system integrity.
- Code Injection & Remote Code Execution: Unvalidated input could allow attackers to inject and run harmful Rexx code.
- Lack of Encryption: Since communications are not encrypted by default, sensitive information and credentials can be intercepted via network sniffing.
Mitigations include:
- Restricting network access through firewalls or binding the daemon to localhost to limit exposure.
- Implementing robust authentication and access controls to prevent unauthorized script invocations.
- Employing tunneling techniques like SSH or VPNs to encrypt communication.
- Regularly auditing and updating the ooRexx environment to address discovered vulnerabilities, and monitoring logs for suspicious activities.
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