start hw4
This commit is contained in:
parent
0524cb1354
commit
d7c965d087
25
hw4/hw4.md
Normal file
25
hw4/hw4.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
# Homework 3: Find the firmware
|
||||||
|
|
||||||
|
We start by copying the firmware capture file from ada to our machine
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
## Reverse Engineering
|
||||||
|
First lets open this capture up in wireshark and do a high level overview
|
||||||
|
|
||||||
|
### Wireshark overview
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
Knowing we are ultimetly looking to re-construct a firmware download, we can discern some important info from wireshark
|
||||||
|
|
||||||
|
* There are 241,531 packets in this capture, but only some are the traffic directly related to this download
|
||||||
|
* Client of the download is 192.168.86.167 and server origin is 192.168.86.228
|
||||||
|
* The download is split over multiple HTTP requests by the shown convention, which themselves are split over multiple TCP requests
|
||||||
|
|
||||||
|
###
|
||||||
|
|
||||||
|
## Questions
|
||||||
|
1) What architecture is the firmware intended to run on?
|
||||||
|
2) What OS is the firmware running?
|
||||||
|
3) What users are present on the system?
|
BIN
hw4/scp-firmware.png
Normal file
BIN
hw4/scp-firmware.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 51 KiB |
BIN
hw4/wireshark-0.png
Normal file
BIN
hw4/wireshark-0.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 240 KiB |
Reference in New Issue
Block a user