High-risk tools in Gdb
10 of the 15 tools in Gdb are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
gdb_breakpointExecuteAdd, delete, enable, disable, list, condition, or clear breakpoints/watchpoints.
-
gdb_contextExecuteReturn registers, instruction, stack, backtrace, breakpoints, and remote context.
-
gdb_execExecuteExecute an arbitrary GDB CLI command with warning-and-confirm risk handling.
-
gdb_loadExecuteLoad a binary, core file, symbol file, and optional program arguments.
-
gdb_memoryExecuteRead, write, block-write, search, or dump inferior memory.
-
gdb_miExecuteExecute a raw GDB/MI command with warning-and-confirm risk handling.
-
gdb_pwndbgExecuteExecute pwndbg/gef/peda-compatible commands through the GDB CLI bridge.
-
gdb_remoteExecuteConfigure or connect local GDB to a remote gdbserver.
-
gdb_run_controlExecuteRun, continue, step, next, stepi, nexti, finish, until, interrupt, kill, or restart.
-
gdb_sessionExecuteStart, stop, restart, or inspect the current GDB session.
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.