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

tx: fix check for short commitments

Public commit record

What the developer wrote

Authored by Jon Griffiths

60/100 · Adequate
tx: fix check for short commitments

Thanks to @erickcestari for reporting and suggesting a fix.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit fixes a bounds-check bug when reading confidential asset or value commitments in Bitcoin/Elements transactions. Before the fix, the code read the first byte of a commitment to decide its type without first confirming that at least one byte remained in the buffer. A malformed, truncated transaction could therefore read one byte past the end of the input data, potentially causing an out-of-bounds read. The patch adds a one-byte length check before that first read.

Recommended action

Review whether this parsing path is reachable from untrusted network input or user-supplied PSBT/transaction data. If so, treat as a security fix and release an advisory or patch note. Add regression tests with truncated commitments to prevent reintroduction.

Security signals we found

01

Out-of-bounds read in transaction deserialization

02

Missing bounds check before reading commitment prefix byte

03

Confidential transaction / asset commitment parsing

04

Fix credited to external reporter @erickcestari

Risk score

Why this scored 60/100

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