1sealsemantic last-mile verification

Research / Finding

clear MuSig nonce-related buffers on error paths

F-LEDGER-BTC-MUSIG-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
LedgerHQ/app-bitcoinReported fixLedgerHQ/app-bitcoin

clear MuSig nonce-related buffers on error paths

fixed in public source; rollout not reverified
details
Finding IDs
F-LEDGER-BTC-MUSIG-001
Status
fixed in public source; rollout not reverified
Disclosure date
Note
nonce-related stack buffers are cleared through a shared cleanup path, including errors. This source-level mapping is limited to secret-buffer cleanup, not all MuSig security properties. Release inclusion and device rollout were not independently checked.

F-LEDGER-BTC-MUSIG-001: Secret handling. MuSig secret buffers are not cleared on the affected path. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-LEDGER-BTC-MUSIG-001

Security area (1seal assessment): Confidentiality. Nonce-derived secret material is cleared before returning from the signing operation. Reviewed 23 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.