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

Merge pull request #559 from LedgerHQ/parse_unhardened

Public commit record

What the developer wrote

Authored by Salvatore Ingala

73/100 · Adequate
Merge pull request #559 from LedgerHQ/parse_unhardened

Always reject hardened derivation steps in `<M;N>` in wallet policies
✓ 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 a boundary bug in how the Ledger Bitcoin app parses wallet policies that use multi-path key expressions like /<M;N>/*. The app was supposed to reject hardened (high-security) derivation indexes, but it incorrectly allowed the exact boundary value 0x80000000 (2,147,483,648) as if it were unhardened. The patch changes the check from 'greater than' to 'greater than or equal to' so that hardened indexes are always rejected. The rest of the changes are minor cleanups: adding 'U' suffixes to numeric constants and using unsigned types in a few places to avoid comparison bugs.

Recommended action

Review whether any already-registered wallet policies or PSBTs could have exploited the accepted hardened boundary value, and confirm the regression test passes. The fix should be included in the next firmware/app release. No immediate user action is required beyond keeping the app updated.

Security signals we found

01

Boundary condition error: hardened derivation index 0x80000000 accepted as unhardened

02

Wallet policy parser validation bypass in multi-path key expressions

03

Regression unit test added for hardened boundary rejection

04

Constants hardened with U suffix to avoid signed/unsigned comparison issues

05

Signed/unsigned comparison cleanups in PSBT signing handlers

Risk score

Why this scored 61/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/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.