Skip to content

DIPS IN SPACE · RESEARCH & PROJECT

STARM · SW-06 · SOFTWARE

Insecure Bootloader

Back to the threat catalogue

STARMDIPS Threat Inventory · catalogue record.

Overwriting startup code with malicious version.

Catalogue severity8/10

Catalogue entries use a 1–10 severity scale. The component matrix uses High, Medium and Low detection priorities.

Target
Startup Logic
Security layer
Bootloader / Firmware
Mitigation
Hardware-anchored Secure Boot.
Mitigation approach
Rule-based: UEFI Secure Boot with hardware root of trust (TPM/HSM).
Immediate response
Re-flash firmware
Machine-learning approaches
Binary classification models, CNNs for firmware fingerprinting, Siamese Networks for firmware similarity detection, One-Class SVM
Methodology
Boot sequence deviations, unexpected firmware hashes, anomalous startup timing, unsigned or modified components
Response role
Embedded Developer
Stage
Manufacturing
Referenced standard
NIST SP 800-193
Catalogue status
Avoided

STARMDIPS Threat Inventory · catalogue record.

Explore matching components and threats

Links are generated from matching terms in the technique title. Explore the component matrix for documented threat–component priorities.

STARMDIPS Threat Inventory · catalogue record.

Related catalogue entries