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

Merge pull request #696 from Foundation-Devices/fix/bootloader-image-bounds

Public commit record

What the developer wrote

Authored by Jacksper13

73/100 · Adequate
Merge pull request #696 from Foundation-Devices/fix/bootloader-image-bounds

SFT-8163: bound the declared image length and fail closed on a timestamp read
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This update fixes two related weaknesses in the Passport hardware wallet's bootloader. First, it corrects a size-limit check so a malicious or malformed firmware update cannot claim a firmware length larger than the actual space reserved for firmware (previously the check allowed a value that was 2048 bytes too big, potentially letting a bad update overwrite adjacent memory). Second, it makes the bootloader refuse to install an update if it cannot read the currently installed firmware's timestamp, preventing an attacker or glitch from bypassing the anti-downgrade protection by making the secure element return zero.

Recommended action

Treat this as a security-relevant bootloader patch. Users should install any firmware release containing this commit and avoid installing firmware from untrusted or MicroSD-based recovery sources until updated. Developers should audit other consumers of fwlength to ensure FW_MAX_FWLENGTH is used consistently.

Security signals we found

01

Bounds-check correction for declared firmware image length

02

Fail-closed behavior added when secure-element timestamp read returns zero

03

Prevention of downgrade bypass via zero/tampered timestamp

04

Header-only length field semantics corrected (fwlength vs total size)

05

Recovery path now clears partial update from SPI flash on failure

Risk score

Why this scored 70/100

Our methodology →
Potential impact 22/30
Exploitability 16/25
Stealth signal 8/15
Affected reach 12/15
Confidence 8/10
Evidence quality 4/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.