CPSA ยท Network device management and Layer 2/3 protocols
TFTP, NTP and Cisco reverse telnet
Config theft via TFTP, NTP abuse and exposure through reverse telnet lines.
Key points
- TFTP (UDP 69): no login or access control; anyone who guesses a filename like hostname-confg can download it.
- Configs hold password hashes, SNMP communities, topology.
- NTP (UDP 123): unauthenticated, so clocks can be skewed, breaking log correlation, certificate checks, time-based controls.
- Cisco reverse telnet: TCP 2000 plus line number reaches an async line (e.g. AUX); exposed lines should refuse connections.
Source: https://www.rfc-editor.org/rfc/rfc1350.html
Practice questions
Which transport and port does TFTP use?
- TCP 21
- UDP 123
- UDP 69
- TCP 69
Show answer
Answer: C. UDP 69
TFTP requests go to UDP port 69. TCP 21 is FTP control and TCP 69 is not TFTP.
What can an attacker gain by skewing the time on devices through unauthenticated NTP?
- Logs that no longer line up between devices
- Certificates that appear expired or not yet valid
- Direct disclosure of enable passwords
- New listening TCP ports on the router
- Interference with time-limited controls
Show answer
Answer: A. Logs that no longer line up between devices, B. Certificates that appear expired or not yet valid, E. Interference with time-limited controls
Wrong time breaks log correlation and certificate validity checks. It does not reveal passwords or open extra ports.
TFTP servers ask for a username and password before sending a file.
Show answer
Answer: False
False. TFTP has no login or access control; servers should expose only files that are safe to be public.
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.
