AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 59 Bitcoin

Add bootloader update

Public commit record

What the developer wrote

Authored by Marko Bencun

28/100 · Opaque
Add bootloader update
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
The short version

What changed, and why it matters

This is a large firmware commit that adds a new two-stage bootloader update mechanism for the BitBox02 hardware wallet. It replaces the old single bootloader with a small, fixed 'stage0' plus a separately signed 'stage1', and ships a special firmware image that can install both stages onto existing devices. The change also updates how firmware signatures are computed so that the product type is included in the hash, which is a security improvement. Because the commit is a major architectural rewrite and includes prebuilt binary blobs whose source is not shown, it carries normal supply-chain and implementation risks, but no specific vulnerability is visible in the diff.

Recommended action

Treat this as a high-risk, security-sensitive release. Verify the prebuilt stage0/stage1 binaries against reproducible builds and audit the new stage0 C code, stage1 signature verification, and firmware installer for memory-safety, downgrade, and rollback issues before shipping. Re-enable the commented-out CI targets only after the stage0 root keys used to sign stage1 are confirmed embedded in the branch.

Security signals we found

01

Bootloader architecture changed from monolithic to two-stage (stage0 + signed stage1).

02

Firmware signature hash now includes a 16-bit product_id, binding firmware to product variant.

03

Root public keys were rotated/replaced with a single set across all products.

04

New stage0 locks debug access (DSU hard lock, security bit) in production builds.

05

Development stage0 skips signature verification and shows a visible cross overlay.

06

Prebuilt stage0/stage1 binary blobs are added to the repository (supply-chain concern).

07

Changelog explicitly calls out 'Security improvements' and a bugfix for full-sized firmware upgrades.

Risk score

Why this scored 59/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 12/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.