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

Enforce MSG_SIGNING_MAX_LENGTH on microSD message signing

Public commit record

What the developer wrote

Authored by Jack

81/100 · Strong
Enforce MSG_SIGNING_MAX_LENGTH on microSD message signing

Restores the file-size cap that the deleted SignTextFileFlow used to
provide before its consolidation in #636. Gated on normal_signing so
health-check files (with their own implicit length constraints) are
unaffected.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit fixes a missing safety limit in the Passport hardware wallet's microSD message-signing feature. Previously, a user could accidentally or maliciously be asked to sign an extremely large file from the microSD card, which could strain memory, cause crashes, or be used in a denial-of-service-style attack. The change restores a maximum file-size check that existed in older code but was lost when two code paths were merged. Health-check files are exempt because they already have their own built-in size limits.

Recommended action

Apply the patch. After applying, verify that MSG_SIGNING_MAX_LENGTH is documented and consistent with available RAM and signing UX limits, and consider adding a regression test that attempts to sign a file larger than the cap.

Security signals we found

01

Restores a previously enforced size cap that was removed during code consolidation

02

Prevents oversized message files from being loaded for signing from removable media

03

Limits memory pressure and potential crash/DoS surface during message signing

04

Gates the check on normal_signing to avoid breaking health-check protocol behavior

Risk score

Why this scored 63/100

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