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

feat(clear_signing): AddressName formatter updated

Public commit record

What the developer wrote

Authored by PrisionMike

77/100 · Adequate
feat(clear_signing): AddressName formatter updated

- When types in (contract,token) we request host for a clear name for the contract.
[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit adds a new optional feature to Trezor's Ethereum clear-signing system. When a transaction field is marked as an address name and its type is 'contract' or 'token', the device can now ask the connected computer (host) to look up a friendly name for that address. If the host provides a name, the device shows that name to the user instead of the raw address. The change is a feature addition, not a direct fix for a known security bug, but it touches the code that decides what text users see on their device screen during transaction approval.

Recommended action

Treat this as a feature commit with security-relevant UI implications rather than an active vulnerability. Reviewers should verify that `lookup_known_address` validates the host response, that the lookup cannot be triggered by untrusted transaction metadata, and that the broad exception handler does not hide integrity failures. Consider whether host-supplied names require the same trust assumptions as other clear-signing metadata.

Security signals we found

01

New host-query path during transaction formatting: `lookup_known_address` is invoked while the user is reviewing a transaction.

02

Broad exception suppression: all non-UnexpectedMessageException errors from the host lookup are silently ignored, which could mask failures or unexpected behavior.

03

User-displayed data now depends on host-provided name lookup, creating a potential UI spoofing surface if the host or lookup source is untrusted or compromised.

04

The feature is gated by a new protobuf flag, so existing definitions default to the prior behavior (lookup_address=false).

05

No changelog entry is present, but the commit title describes a feature update, not a security fix.

Risk score

Why this scored 26/100

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