1sealsemantic last-mile verification

Research / Finding

bound preimage writes by the output buffer capacity

F-LEDGER-BTC-PREIMAGE-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

bound preimage writes by the output buffer capacity

fixed in public source; rollout not reverified
details
Finding IDs
F-LEDGER-BTC-PREIMAGE-001
Status
fixed in public source; rollout not reverified
Disclosure date
Note
call_get_preimage now rejects an oversized preimage and checks buffer writes. The finding-to-patch mapping is based on the reported callsite and public diff, not public attribution of this finding ID. A fixed release and device rollout were not independently checked.

F-LEDGER-BTC-PREIMAGE-001: Memory safety. Preimage writes require an explicit destination-buffer bound. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

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

Security area (1seal assessment): Memory safety. The patch bounds writes to a caller-provided preimage buffer. 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.