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

feat(core): allow reading out of telemetry data

Public commit record

What the developer wrote

Authored by tychovrahe

57/100 · Thin
feat(core): allow reading out of telemetry data

[no changelog]
✓ 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 commit adds a new read-only feature that lets the host computer ask a Trezor device for internal telemetry records: minimum/maximum temperature and battery error counts. It is a feature addition, not a fix. There is no direct evidence in the commit that this introduces a security vulnerability, but it does expose previously internal device data over the USB/Protobuf interface. The security relevance depends on whether the new TelemetryGet message is protected by an existing session/access policy or can be requested by any connected host.

Recommended action

Verify whether TelemetryGet requires an authorized session or unlocked device before returning telemetry. If it can be invoked by any connected host, consider adding a session-policy check or requiring device unlock. Review the telemetry_get C implementation for side channels and ensure the returned battery_errors bitfield does not leak sensitive diagnostic information. Add a changelog entry for traceability.

Security signals we found

01

New host-facing Protobuf message handler added without visible in-handler authorization

02

Previously internal secure-subsystem data (battery_errors, temperature extrema) exposed to host

03

Feature is model-gated (T3W1 revC) and compile-time conditional, limiting exposure

04

No changelog entry provided despite user-visible feature addition

05

No input parsing or memory allocation beyond fixed-size tuple creation

Risk score

Why this scored 22/100

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