This document is not yet written.
Once you've identified the relevant ports exposed by the device, you should identify relevant tools that you can use to inspect the applications running on those ports. During this step it can be helpful to understand the intended behavior and user experience for the device. It also is a good place to start taking notes on inputs of the device (e.g. firmware update fields, potentially un-sanitized user input fields). If you can login to a command line prompt, is it restricted or a real shell? If you have a shell is it as a user or root? What other user's exist in
Initially, accessing the various port could be as simple as a web browser or
curl for ports 80 or 443. Sometimes using Chrome or Firefox developer tools can illuminate interfaces that aren't obvious from the rendered view. For port 161 or 162 you can use snmpget or snmpwalk (given you know the credentials). For ftp (port 21), ssh (port 22), telnet (port 23), you can use your favorite client to try to connect without credentials, with default credentials, or whatever credentials you may have.
Take away: Now that you have a surface to work on, be resourceful in determining ways to work with that surface.
End User Serial Port (UART)
Some systems provide a management port or serial access that is out side the influence of the network. The reason we want to connect to a serial port is so we can potentially:
- Observe boot up messages that may present themselves before any logging or system services are available. Often kernels will just start outputting their boot state to the default system console. This console in practice is mapped to the serial port that we're attempting to connect to.
- Control boot loaders. Some boot loaders like U-boot have a lot of useful analysis capabilities as well as the ability to modify system state.
- Console access to the system. Often if you have serial access, the developers assume you have physical access to a device and therefore security isn't a factor, presenting you with root or some other administrator user interface.
A common looking interface for these serial ports are DB9 connectors that support full UART protocol. Other connections that I've personally seen include RJ11 connectors, RJ45 connectors, and even 3.5" headphone jack connectors.
- No Lab ... Unrestricted Access via UART/JTAG later in course.