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

feat(cardano): reject probable hashes

Public commit record

What the developer wrote

Authored by Peter Jaško

57/100 · Thin
feat(cardano): reject probable hashes
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This update makes Trezor's Cardano message-signing feature refuse to sign 28-byte payloads that look like cryptographic hashes. The goal is to prevent users from accidentally signing a hash of an unknown message, which could let an attacker trick them into authorizing something they did not read. The change is a simple heuristic: if the payload is exactly 28 bytes and is not made of ordinary printable text, the device now rejects it with an error.

Recommended action

Review the heuristic for false positives: legitimate 28-byte binary messages that are not hashes will also be rejected. Consider whether the device should support explicit hash signing with a distinct user flow in the future, and document the limitation clearly for Cardano users and integrators.

Security signals we found

01

New input-validation guard added to a signing path

02

Heuristic rejection of hash-length payloads to prevent signing blind hashes

03

Test fixture added for the new failure mode

Risk score

Why this scored 36/100

Our methodology →
Potential impact 8/30
Exploitability 7/25
Stealth signal 6/15
Affected reach 5/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.