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

Merge pull request #678 from Foundation-Devices/SFT-8071-psbt-parsing-rejects-unknown-fields

Public commit record

What the developer wrote

Authored by mjg-foundation

58/100 · Thin
Merge pull request #678 from Foundation-Devices/SFT-8071-psbt-parsing-rejects-unknown-fields

SFT-8071: fixed unknown unknowns
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This firmware update fixes how Passport handles partially-signed Bitcoin transactions (PSBTs) that contain fields the device does not recognize. Previously, unknown fields could accidentally be interpreted as known Taproot key-derivation data, which could corrupt the transaction or leak path information. The patch makes all unrecognized fields pass through unchanged, adds support for the standard PSBT version field, and rejects unsupported PSBT versions. It also adds unit tests to verify the behavior.

Recommended action

Treat as a security-relevant hardening fix. Review whether prior firmware versions could be coerced into mis-serializing unknown Taproot-like fields, and consider whether a CVE or advisory is warranted if transaction integrity or key-path privacy could be affected. Users should upgrade to a firmware containing this commit.

Security signals we found

01

PSBT unknown-field type confusion between maps could lead to misinterpretation of attacker-controlled data as Taproot derivation info

02

Missing PSBT version handling could allow future-version PSBTs to be parsed with undefined semantics

03

Added explicit rejection of malformed and duplicate PSBT_GLOBAL_VERSION fields

04

Unknown fields now bypass type-specific serialization, preventing structured decoding of opaque data

05

Unit tests added for unknown-field round-trip fidelity and version validation

Risk score

Why this scored 63/100

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