Firmware Analysis Firmware security and vulnerability scanning commands.
Binarly The Binarly test step executes a scan using the Binarly service to analyze firmware binaries.
For more information, visit Binarly Risk Hunt .
Attribute Type Required Default Description cmdconstYes binarly Must be binarly report namestringYes Uniquely identifies the test step in reports and logs parametersBinarlyParametersYes Binarly-specific parameters optionsOptionsObjectNo Additional command options
Binarly Parameters Attribute Type Required Description tokenstringYes Authentication token for Binarly service file_pathstringYes Path to the binary file to be scanned
Binarly Example cmd : binarly report
name : "Scan BIOS for vulnerabilities"
parameters :
token : "your-binarly-token"
file_path : "/path/to/firmware.bin"
options :
timeout : "10m" # Scan might take a while ChipSec Run ChipSec on the DUT.
Attribute Type Required Default Description cmdconstYes chipsecCommand Name namestringYes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transportTransportObjectNo Additional transport options optionsOptionsObjectNo Additional command options parametersChipSecOptionsYes Options passed into ChipSec
ChipSec Options Attribute Type Required Default Description modules[]stringYes List of modules that get executed from the ChipSec test suite pchstringNo PCH parameter that gets passed into ChipSec as --pch parameter platformstringNo Platform parameter that gets passed into ChipSec as --platform parameter
ChipSec Example cmd : chipsec
name : Run chipsec tests
transport :
proto : ssh
options :
host : "[[attributes.Host]]"
user : root
password : root
parameters :
modules :
[
common.bios_kbrd_buffer,
common.bios_smi,
common.bios_ts,
common.bios_wp,
common.ia32cfg,
common.me_mfg_mode,
common.memlock,
common.rtclock,
common.smm,
common.smrr,
common.spi_access,
common.spi_desc,
common.spi_fdopss,
common.spi_lock,
common.uefi.access_uefispec,
common.memconfig,
common.remap,
common.smm_dma,
] Firmware Version Check the ESRT Firmware version entry on the DUT.
Attribute Type Required Default Description cmdconstYes firmware versionCommand Name namestringYes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transportTransportObjectYes Additional transport options optionsOptionsObjectNo Additional command options parametersFirmwareVersionOptionsYes Options passed into the firmware version cmd
Firmware Version Options Attribute Type Required Default Description formatstringNo numberFormat of the tool’s output. Available options: number, hex, pair, triplet, quad. expectFirmware Version Expect OptionsYes Expected Options
Firmware Version Expect Options Attribute Type Required Default Description versionstringYes expectExpected firmware version in the specified format.
Firmware Version Example cmd : firmware version
name : Get firmware version (ESRT)
transport : *transport
parameters :
format : pair
expect :
version : "1.11" FWHunt Run Firmware Hunt on the firmware binary file.
Attribute Type Required Default Description cmdconstYes fwhuntCommand Name namestringYes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI optionsOptionsObjectNo Additional command options parametersFWHuntOptionsYes Options passed into the fwhunt cmd
FWHunt Options Attribute Type Required Default Description pathstringYes Path of the binary to be analyzed. rules_dirs[]stringNo List of directories to search for rules. If not specified, the default rules directory will be used. rules[]stringNo List of rules to run.
FWHunt Example name : FwHunt Test
steps :
- cmd : fwhunt
name : Run FwHunt tests
parameters :
path : "[[input.Binary]]" FWTS Run Firmware Test-Suite on the DUT.
Attribute Type Required Default Description cmdconstYes fwtsCommand Name namestringYes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transportTransportObjectYes Additional transport options optionsOptionsObjectNo Additional command options parametersFWTS OptionsYes Options passed into the fwts cmd
FWTS Options Attribute Type Required Default Description flags[]stringNo List of flags to pass to fwts.
FWTS Example cmd : fwts
name : Run Firmware Testsuite tests
options :
timeout : 10m
transport : *transport
parameters :
flags : [-b] HSI Report Host Firmware Security on the DUT.
Attribute Type Required Default Description cmdconstYes hsiCommand Name namestringYes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transportTransportObjectYes Additional transport options
HSI Example cmd : hsi
name : Report Host Firmware Security
options :
timeout : 10m
transport : *transport