Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Firmware extraction obtains the software image from an embedded device; firmware analysis unpacks that image and examines it for hardcoded secrets, vulnerable components, and weak update logic.

What Is Firmware Extraction and Analysis?
Firmware is the software that makes a piece of hardware behave like a product. Extracting it means obtaining that image — from a vendor download, a flash chip, or a debug port — and analysing it means taking it apart to see what the manufacturer actually shipped. It is the single highest-yield activity in an embedded security assessment, because everything the device knows is in there: the credentials, the keys, the update logic, and every third-party library whose version nobody tracked.
Testers work down this list, stopping at the first that succeeds.
dd from /dev/mtdblock* copies the partitions out over the same connection or across the network.flashrom and a CH341A programmer or Bus Pirate dumps the contents without desoldering anything.Intercepting an over-the-air update is a sixth route and often the most instructive, since it reveals the update mechanism at the same time.
A raw dump is rarely a filesystem. binwalk scans for signatures and identifies bootloaders, kernels, and compressed archives; sasquatch handles the non-standard SquashFS variants that vendors love; ubi_reader deals with UBIFS on NAND. Checking entropy comes first — an image with uniformly high entropy throughout is encrypted or compressed as a whole, and the key is usually fused into the SoC, at which point the SPI route stops working and you go back to the debug interface.
Once a filesystem is mounted, the structure is familiar: /etc, /bin, a web root, and a handful of vendor binaries that do the interesting work.
/etc/shadow hashes that crack in seconds, API tokens in configuration files, Wi-Fi keys, and database passwords.Automated platforms such as EMBA, FACT, and the Firmware Analysis Toolkit run the common checks, match components against vulnerability data, and highlight anomalies, which is a sensible first pass before manual work. For reverse engineering specific binaries, Ghidra handles MIPS and ARM comfortably and is free.
Emulation turns static review into dynamic testing. qemu-user with chroot runs individual binaries; full-system emulation through FirmAE or Firmadyne can bring a router’s web interface up on a laptop, where it can be fuzzed and exploited without risking the hardware. Emulation often fails on peripheral access, which is why a physical sample still matters.
Analysing firmware from a device you own is lawful, but the surrounding activity needs care. Testing anything you do not own requires written authorisation under the Computer Misuse Act 1990, and publishing findings should follow coordinated disclosure, for which the NCSC provides guidance and most manufacturers now publish a contact under the PSTI regime. Keep extracted images inside the engagement scope; they frequently contain customer data as well as vendor code.
Our Hardware Penetration Test Services include firmware extraction and review as standard, with findings mapped back to the design decisions that caused them.
Check whether the decryption key is recoverable. Many devices decrypt in the bootloader using a key held in the SoC, so reading internal RAM over JTAG after boot gives you the plaintext. Others reuse a key across models that has already been published. If the chip enforces flash encryption properly and debug is fused off, extraction may genuinely be infeasible without side-channel or fault injection work.
Not always. A published update package supports most static analysis, including component inventory, credential discovery, and review of update logic. You need hardware to confirm that findings are exploitable, to test interfaces the image cannot tell you about, and to reach firmware that is never released publicly. Most engagements combine a downloaded image with one or two sample units.
Extraction ranges from minutes for a public download to a day or more when debug interfaces are locked and a chip has to come off. Analysis of a typical consumer router image takes two to four days for a thorough pass: unpacking, component inventory, credential and key hunting, review of the web interface binaries, and emulation of the parts worth attacking dynamically.
They can make it expensive rather than impossible. Encrypted external flash with a fused key, blown debug fuses, secure boot, and anti-tamper packaging push the cost towards laboratory techniques such as fault injection or decapping. The more useful goal is to ensure extraction is not catastrophic: no shared keys, no hardcoded credentials, and no secrets in the image worth stealing.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.