CommitWatch RSS
AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 29 Bitcoin

SFT-4441: Update Rust dependencies.

FDefd6bdb3 View source ↗
Public commit record

What the developer wrote

Authored by Jean-Pierre De Jesus DIAZ

45/100 · Thin
SFT-4441: Update Rust dependencies.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit updates several Rust library dependencies used in the Passport hardware wallet firmware and makes small code adjustments to match the new library versions. The most notable change is in the cryptographic signing code, where the code no longer wraps the data in a 'Message' object before creating a Schnorr signature. On its own, this looks like a routine compatibility update, but because it touches security-critical code (digital signatures), it warrants careful review to ensure the new calling pattern is safe and does not bypass any intended message-validation step.

Recommended action

Review the secp256k1 0.30 changelog and migration notes to confirm the API change is intentional and safe. Verify that every call site of `secp256k1_sign_schnorr` supplies a 32-byte digest and that the firmware's higher-level code still hashes/validates messages before reaching this function. Run the project's cryptographic test suite and, if available, fuzz or property-test the signing path. Treat this as a routine but security-relevant dependency update rather than an active vulnerability unless additional evidence emerges.

Security signals we found

01

Cryptographic signing API change: removal of Message wrapper in Schnorr signing path

02

Dependency version bumps for security-sensitive crates (secp256k1, bitcoin_hashes)

03

No explicit security advisory, CVE, or vendor security note present in commit or supplied references

04

No input-length or digest-validation checks visible in the changed signing function

Risk score

Why this scored 29/100

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

More from Passport firmware

Related watches

Moderate 57 AI analysisMessage 55 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

Preserve hardened firmware verification result

This bootloader patch changes how the result of a security check on the currently-running firmware is stored. Previously, the code immediately converted the secure verification result into a plain true/false boolean. Now it keeps the speci…

Hardened firmware verification result preservationReplacement of bool with secresult for security-critical return valueBootloader update path depends on firmware validity check
a6efb276by Jack+5−51 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 35 · Opaque
FD FoundationPassport firmware BitcoinHardware wallets

Harden firmware update validation

This commit changes how Passport's bootloader checks firmware updates. Previously, if the currently-running firmware failed validation, the bootloader would skip verifying the new update's signature and could install it anyway. Now the new…

Bypassed/missing cryptographic verification path hardenedFirmware update signature check moved to unconditional executionCurrent firmware invalid state no longer skips new firmware signature verification
b157473cby Jack+30−261 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 50 · Thin
FD FoundationPassport firmware BitcoinHardware wallets

SFT-6378: removed more branching from mnemonic decode process

This commit tweaks the code that converts a user's BIP39 recovery phrase (mnemonic words) into secret bits inside a hardware wallet. The change removes an 'if' branch during word copying so the loop always writes to the same positions, reg…

Branchless, constant-time-style copy of sensitive input wordsMasking of post-delimiter bytes to zero to avoid information leakage via memory access patternsRemoval of conditional stores that depended on word length
d0edb18aby Matt Gleason+13−71 file
Vendor flagged security relevance
Open full analysis →Source commit ↗