Traffic interception

The r-commands encrypt nothing, so a positioned attacker captures the passwords rexec/rlogin send, every command and its output, and whole sessions. The cleartext, setup-only-authenticated streams can be hijacked to inject commands and replayed, giving credentials, data, and execution without defeating authentication.

1 phút đọccập nhật 7 thg 10, 2026florianamette1 người đóng góp
Hỏi trợ lý của bạn (MCP)Sửa trên GitHub

None of the r-commands encrypt their traffic, so an on-path attacker can read what they carry: the cleartext passwords sent by rexec and password-fallback rlogin, commands and output, and complete interactive sessions. Beyond passive capture, an attacker who remains on path may inject correctly sequenced data into a live TCP stream after authentication. A saved TCP exchange cannot simply be replayed as a new authenticated session because a new connection has different TCP state and must satisfy the service's authentication again.

bash
# capture all TCP traffic for the target so negotiated secondary streams are included
tcpdump -i eth0 -w rcmds.pcap 'tcp and host <target>'
# enumerate streams before following the relevant service and secondary connections
tshark -r rcmds.pcap -q -z conv,tcp
tshark -r rcmds.pcap -q -z follow,tcp,ascii,<stream-number>

Subtopics#

References#