CPSA ยท Network device management and Layer 2/3 protocols
Telnet, SSH and web management of network devices
Clear-text vs encrypted management and weaknesses of device web interfaces.
Key points
- Telnet (TCP 23): usernames, passwords and commands in clear text; anyone on the path can read or hijack the session.
- SSH (TCP 22): encrypted; version 2 is safe, version 1 has known design flaws.
- Device web interfaces: plain HTTP exposes credentials and cookies; embedded servers often have default accounts, old firmware, weak sessions.
- Tester checks: reachable services, their versions, limits to a management network.
Practice questions
Which TCP port does Telnet use by default?
- TCP 21
- TCP 22
- TCP 23
- TCP 25
Show answer
Answer: C. TCP 23
Telnet listens on TCP 23. Port 22 is SSH, 80 is HTTP and 443 is HTTPS, so none of those identify Telnet.
Which of these are weaknesses commonly found on device web management interfaces?
- Default administrator credentials left unchanged
- Login forms served over plain HTTP
- Public key authentication for the admin account
- Pages written in HTML
- Access restricted to a management VLAN
Show answer
Answer: A. Default administrator credentials left unchanged, B. Login forms served over plain HTTP
Default credentials and HTTP without TLS are classic findings. SSH key authentication and the fact that a page uses HTML are not weaknesses.
Enabling SSH on a device means Telnet is automatically disabled.
Show answer
Answer: False
False. On Cisco IOS the VTY lines accept whatever 'transport input' allows, so Telnet stays available until the administrator restricts it to SSH.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
