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

Make sure raw_witnessUtxo is long enough before reading its 9th byte

Public commit record

What the developer wrote

Authored by Salvatore Ingala

50/100 · Thin
Make sure raw_witnessUtxo is long enough before reading its 9th byte
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a length check in the Ledger Bitcoin app's PSBT signing code. Before reading the 9th byte of a witness UTXO field, the code now verifies the field is at least 9 bytes long. Previously, it only checked that some data was returned, which could lead to reading past the end of a malformed or truncated input. This is a defensive fix against an out-of-bounds read that could affect transaction amount calculations during signing.

Recommended action

Treat this as a security-relevant hardening fix. Review related PSBT parsing functions for similar insufficient-length checks, and include this patch in the next firmware release. If a CVE is desired, request one from a CNA; no CVE is present in the commit materials.

Security signals we found

01

Out-of-bounds read prevented by length check

02

PSBT witness UTXO parsing hardening

03

Memory safety fix in cryptographic signing path

04

Potential denial-of-service or information disclosure via malformed PSBT

Risk score

Why this scored 59/100

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