Port 2159GDB Remote Debug Port

GDB Remote Debug Port for debugger-to-target connections.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
8/10

risk

lookups
0

rank 993 of 5,713 · top 17%

also known as GDB remote debugging

Technical Details

what runs on :2159

The service uses the GDB Remote Serial Protocol, usually carried over a TCP connection between GDB and gdbserver or another remote target stub. Packets are framed as $payload#checksum, with acknowledgements and capability negotiation such as qSupported; subsequent packets read and write registers or memory, control execution, and report stop events. The IANA registration includes UDP, but ordinary GDB remote debugging uses TCP, serial links, or other explicitly configured transports; the port number is not a requirement of every GDB deployment.

Security Information

exposure of :2159

risk score

8/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

remote access averages 3.8 across 217 ports — this one sits 4.2 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

A remotely reachable GDB stub is a powerful control interface, typically without encryption or meaningful authentication. A client that can connect may inspect or modify process memory and registers and control execution, so this port should be restricted to a trusted management or development network and protected with firewall rules or a secure tunnel rather than exposed to the Internet.

the 8 most looked-up other ports in remote access — 217 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted