Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:guide-developer:adding_new_device [2019/09/03 14:22] – [Learn by example] brianpow | docs:guide-developer:adding_new_device [2024/10/22 09:39] – Add note about using curl as an option. evs | ||
|---|---|---|---|
| Line 24: | Line 24: | ||
| ==== Search by Git commit ==== | ==== Search by Git commit ==== | ||
| - | Browse the source | + | [[https:// |
| - | Search | + | |
| ===== Important files ===== | ===== Important files ===== | ||
| Line 115: | Line 115: | ||
| ==== Getting a shell on the target device ==== | ==== Getting a shell on the target device ==== | ||
| In order to collect relevant data for a port of OpenWrt to the device of interest one wants shell access. Most devices though do not offer a way to get a shell with telnet or ssh. | In order to collect relevant data for a port of OpenWrt to the device of interest one wants shell access. Most devices though do not offer a way to get a shell with telnet or ssh. | ||
| + | === Abuse Unsanitized User Input === | ||
| + | Some router offers ping test or NTP server configuration and may not properly sanitize user input. Try to enter shell script and see if you are lucky. You may need some '' | ||
| + | == Starting telnetd == | ||
| + | <code bash> | ||
| + | $( / | ||
| + | </ | ||
| + | == Obtain the password hash using HTTP or use '' | ||
| + | <code bash> | ||
| + | $( cp /etc/shadow /www ) | ||
| + | $( cp /etc/passwd /www ) | ||
| + | </ | ||
| + | Then try to download them to your computer and crack the hash | ||
| + | === Downgrade to older firmware === | ||
| + | Some router may try to download a firmware file (e.g. [[toh: | ||
| + | |||
| + | === Downgrade by Serial access === | ||
| + | Serial access may allow you to enter console mode of u-boot for flashing/ | ||
| + | See [[docs: | ||
| + | |||
| + | === HTTP Server Vulnerability === | ||
| + | Some routers may be running outdated/ | ||
| + | |||
| + | === Netgear === | ||
| With [[toh: | With [[toh: | ||
| When such means cannot be used, one could try to flash an image build from the sources published by the vendor with telnetd enabled. | When such means cannot be used, one could try to flash an image build from the sources published by the vendor with telnetd enabled. | ||
| Line 125: | Line 148: | ||
| Typically one can use the following commands: | Typically one can use the following commands: | ||
| - | | + | |
| - | cat / | + | <code bash> |
| - | cat / | + | dmesg # log buffer might be to small, see note 1. |
| - | cat / | + | cat / |
| - | cat / | + | cat / |
| - | ls / | + | cat / |
| - | cat /proc/mtd | + | cat / |
| - | cat / | + | ls / |
| - | ifconfig -a | + | cat /proc/mtd |
| - | ls / | + | cat / |
| - | brctl show | + | ifconfig -a |
| - | + | ls / | |
| + | brctl show | ||
| + | cat / | ||
| + | </ | ||
| **Note 1:** Often the log buffer is to small and the earliest messages may be missing from the information retrieved with '' | **Note 1:** Often the log buffer is to small and the earliest messages may be missing from the information retrieved with '' | ||
| Line 144: | Line 171: | ||
| ==== Getting collected data from a device ==== | ==== Getting collected data from a device ==== | ||
| - | Sometimes no normal means such as scp or ftp are available | + | Because of the limited space, common file transfer utilities |
| - | Assume the files with relevant data on the device with IP address | + | |
| - | On the device do: | + | Assume the router ip is '' |
| - | | + | |
| - | | + | === HTTP by '' |
| - | After that the data on the host connected | + | If the web interface are served from ''/ |
| - | | + | |
| - | + | == Sender == | |
| + | <code bash> | ||
| + | mount -o bind /tmp /www | ||
| + | </ | ||
| + | |||
| + | == Receiver == | ||
| + | <code bash> | ||
| + | wget http:// | ||
| + | </ | ||
| + | |||
| + | === FTP by '' | ||
| + | == Receiver == | ||
| + | Setup an FTP server. Add an anonymous account with write permission | ||
| + | |||
| + | <code bash> | ||
| + | python -m pyftpdlib -w -p 21 | ||
| + | </ | ||
| + | == Sender == | ||
| + | <code bash> | ||
| + | busybox ftpput 192.168.0.123 | ||
| + | </ | ||
| + | |||
| + | === netcat by '' | ||
| + | == Receiver == | ||
| + | <code bash> | ||
| + | busybox nc -l -p 12345 > important-data.txt | ||
| + | </ | ||
| + | == Sender == | ||
| + | <code bash> | ||
| + | cat /tmp/important-data.txt | busybox nc 192.168.0.123: | ||
| + | </ | ||
| + | |||
| + | === TFTP by '' | ||
| + | == Receiver == | ||
| + | Setup a tftp server | ||
| + | |||
| + | == Sender == | ||
| + | <code bash> | ||
| + | busybox tftp -p -l / | ||
| + | </ | ||
| + | |||
| + | === Use Curl to upload === | ||
| + | Depending on what is compiled into your curl binary if available you may also be able to auth, use ftp/tftp etc. | ||
| + | "It supports these protocols: DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, | ||
| + | HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, | ||
| + | and WSS. The command is designed to work without user interaction. | ||
| + | " | ||
| + | Extract from curl man page: | ||
| + | < | ||
| + | -T, --upload-file < | ||
| + | This transfers the specified local file to the remote URL. If there is no file part in the specified URL, curl will append | ||
| + | the local file name. NOTE that you must use a trailing / on the last directory to really prove to Curl that there is no | ||
| + | file name or curl will think that your last directory name is the remote file name to use. That will most likely cause the | ||
| + | upload operation to fail. If this is used on an HTTP(S) server, | ||
| + | |||
| + | Use the file name " | ||
| + | riod) may be specified instead of " | ||
| + | uploaded. | ||
| + | |||
| + | You can specify one -T, --upload-file for each URL on the command line. Each -T, --upload-file + URL pair specifies what to | ||
| + | upload and to where. curl also supports " | ||
| + | files to a single URL by using the same URL globbing style supported in the URL. | ||
| + | |||
| + | When uploading | ||
| + | set of headers and mail body formatted correctly by the user as curl will not transcode nor encode it further in any way. | ||
| + | |||
| + | -T, --upload-file can be used several times in a command line | ||
| + | |||
| + | Examples: | ||
| + | curl -T file https://example.com | ||
| + | curl -T " | ||
| + | | ||
| + | |||
| + | See also -G, --get and -I, --head. | ||
| + | |||
| + | </ | ||
| + | === Copy from terminal === | ||
| + | If all of the above tools/ | ||
| + | |||
| + | base64 would be a common choice to work around this limitation, but many routers lack such a command. You can first escape binary data to screen-safe hexadecimal by piping to busybox hexdump on the router: | ||
| + | <code bash> | ||
| + | hexdump -v -e '/1 " | ||
| + | </ | ||
| + | You can then reverse it on the computer with the following command: | ||
| + | <code bash> | ||
| + | xxd -r -p | ||
| + | </ | ||
| + | |||