Port 1 Details
known port assignments and vulnerabilities
threat/application/port search:
Port(s) |
Protocol |
Service |
Details |
Source |
1 |
udp |
tcpmux |
TCP Port Service Multiplexer (IANA registered)
Sockets des Troie remote access trojan uses this port (a.k.a. Backdoor.Sockets23, Lame, Backdoor.Kamikaze, IRC_trojan, TROJ_Backdoor, W32/Cheval.gen, coded in Delphi 3, 06.1998). It might also use ports 1/udp, 5000, 5001, 30303, 50505, 60000 and 65000. |
SG
|
1 |
tcp |
tcpmux |
Scans against this port are commonly used to test if a machine runs SGI Irix (as SGI is the only system that typically has this enabled). This service is almost never used in practice.
RFC1078 - TCPMUX acts much like Sun's portmapper, or Microsoft's end-point mapper in that it allows services to run on arbitrary ports. In the case of TCPMUX, however, after the "lookup" phase, all further communication continues to run over that port.
builtins.c in Xinetd before 2.3.15 does not check the service type when the tcpmux-server service is enabled, which exposes all enabled services and allows remote attackers to bypass intended access restrictions via a request to tcpmux port 1 (TCP/UDP).
References: [CVE-2012-0862] [BID-53720] [OSVDB-81774]
Trojans that use this port: Breach.2001, SocketsDeTroie
Also see: CERT: CA-95.15.SGI.lp.vul |
SG
|
1 |
tcp,udp |
|
TCP Port Service Multiplexer (official) |
Wikipedia
|
1 |
udp |
trojan |
[trojan] Sockets des Troie |
Trojans
|
1 |
tcp |
tcpmux |
TCP Port Service Multiplexer [rfc-1078] |
SANS
|
1 |
udp |
SocketsdesTroie |
[trojan] Sockets des Troie |
SANS
|
1 |
udp |
tcpmux |
TCP Port Service Multiplexer |
SANS
|
1 |
tcp |
tcpmux |
TCP Port Service Multiplexer [rfc-1078] |
Nmap
|
1 |
udp |
tcpmux |
TCP Port Service Multiplexer |
Nmap
|
1 |
tcp,udp |
tcpmux |
TCP Port Service Multiplexer |
IANA
|
|
10 records found
|
jump to:
|
Related ports: 5000 5001 30303 50505 60000 65000
« back to SG Ports
External Resources
SANS ISC: port 1
Notes:
Port numbers in computer networking represent communication endpoints. Ports are unsigned 16-bit integers (0-65535) that identify
a specific process, or network service. IANA is responsible for internet protocol resources, including the registration of commonly
used port numbers for well-known internet services.
Well Known Ports: 0 through 1023.
Registered Ports: 1024 through 49151.
Dynamic/Private : 49152 through 65535.
TCP ports use the Transmission Control Protocol, the most commonly used protocol
on the Internet and any TCP/IP network. TCP enables two hosts
to establish a connection and exchange streams of data. TCP guarantees delivery of data
and that packets will be delivered in the same order in which they were sent.
Guaranteed communication/delivery is the key difference between TCP and UDP.
UDP ports use the Datagram Protocol. Like TCP, UDP is used in combination with IP (the Internet Protocol)
and facilitates the transmission of datagrams from one computer to applications on another computer,
but unlike TCP, UDP is connectionless and does not guarantee reliable communication; it's up to the application that received
the message to process any errors and verify correct delivery. UDP is often used with time-sensitive
applications, such as audio/video streaming and realtime gaming, where dropping some packets is preferable to waiting for delayed data.
When troubleshooting unknown open ports, it is useful to find exactly what services/processes are listening to them.
This can be accomplished in both Windows command prompt and Linux variants using the "netstat -aon" command.
We also recommend runnig multiple anti-virus/anti-malware scans to rule out the possibility of active malicious software.
For more detailed and personalized help please use our forums.
Please use the "Add Comment" button below to provide additional information or comments about port 1.
|
|
|