Port 369RPC2 Port Mapper

Port 369 is officially assigned to the RPC2 Port Mapper service, which functions similarly to the classic portmapper for Remote Procedure Call-based services. This port enables clients to locate other RPC2 services dynamically by providing the necessary mapping information. Its operation is vital in distributed environments relying on RPC2 to facilitate seamless communication between distributed components..

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
11,093

rank 383 of 993 · top 39%

Technical Details

what runs on :369

Technical Overview

RPC2 (Remote Procedure Call Version 2) is a protocol designed to facilitate remote procedure calls, extending earlier RPC systems with enhanced features and capabilities geared toward distributed systems. The RPC2 Port Mapper listens on port 369 and serves as a registry that maintains a database of active RPC2 services and their corresponding network endpoints. When a client requires access to an RPC2 service, it queries the Port Mapper to determine the port number on which the desired service is listening.

How It Works

Upon registration, RPC2 services inform the Port Mapper of their availability, supplying details such as the program's unique identifier and listening port. This allows clients to dynamically discover services instead of relying on hardcoded port numbers. The Port Mapper supports both TCP and UDP protocols, allowing flexibility in communication types based on reliability and overhead requirements.

Protocols and Deployments

The RPC2 protocol stack generally operates over IP networks and modularly supports other protocols layered atop for secure remote interactions. Because of its dynamic nature and registration capabilities, RPC2 is utilized widely in distributed file systems, network management tools, and certain research or legacy Unix environments where modular and dynamic service location is advantageous.

Security Information

exposure of :369

risk 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 · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Common Vulnerabilities

  • Unauthenticated Queries: The RPC2 Port Mapper typically responds to any query without authentication, enabling attackers to perform reconnaissance and map available RPC2 services.
  • Service Enumeration: Attackers exploit open Port Mappers to discover services for potential targeting or exploitation.
  • Amplification & Reflection Attacks: Malformed queries can be used as part of denial-of-service attacks.
  • Exploiting Weaknesses in Registered Services: Vulnerable RPC2 services registered on the Port Mapper can be easily targeted once discovered.

Mitigations

  • Access Controls: Implement strict firewall policies to restrict access to port 369 only to trusted hosts on both TCP and UDP.
  • Segmentation: Isolate RPC2 services and the port mapper from public or untrusted networks.
  • Disable When Unused: If RPC2 is not in use, disable the service to reduce attack surface.
  • Monitoring: Regularly audit network traffic and RPC2 port registrations for suspicious activity.
  • Authentication & Encryption: Where possible, enforce strong authentication and consider tunneling RPC2 traffic through secure channels such as SSH or VPN.

the 8 most looked-up other ports in network services — 604 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted