Skip to the content ForoHackers
Log inJoin

Firmware analysis: start here

Firmware analysis
#3293 · · Quote · Report

Firmware analysis is the examination of the software inside devices such as routers, cameras and controllers, to learn how it works and whether it is safe. Analyse only devices you own or are authorised to test, and images made for training. It is how researchers and vendors find weak updates, hard-coded secrets and outdated components before they cause harm.

Key concepts

  • Obtaining an image: from the vendor's update file, or read from the device's own memory, on hardware you own.
  • Unpacking: images are layers of headers, compression and filesystems that you peel until files appear.
  • Inventory: which components and versions are inside, and what is known about them.
  • Secrets and configuration: keys, passwords and debug features that should not ship.
  • Update integrity: whether images are signed and verified, and whether an older, weaker image can be installed.

Vocabulary

  • Squashfs: a common compressed read-only filesystem in embedded Linux images.
  • SBOM: software bill of materials, a list of what is in a build.
  • Entropy analysis: measuring randomness to find compressed or encrypted regions.
  • UART and JTAG: debug interfaces on a board, which a vendor should disable or protect.

What to study, in order

  1. Embedded Linux basics: boot, filesystems, init and services.
  2. Unpack an open-source router firmware image with standard tools and list its contents.
  3. Build a component inventory and compare it with published advisories.
  4. Search an image you built yourself for strings, keys and configuration files, and note what should not be there.
  5. Read how signed updates and secure boot work, and what a failed check should do.

Related tags

#firmware #binary-analysis #embedded-linux #hardware-security #reverse-engineering

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply