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

feat(core/prodtest): allow reading and resetting telemetry data in prodtest

Public commit record

What the developer wrote

Authored by tychovrahe

62/100 · Adequate
feat(core/prodtest): allow reading and resetting telemetry data in prodtest

[no changelog]
✓ Specific, 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 two new factory-test commands to Trezor's production-test firmware: one that reads battery telemetry (temperature extremes, error flags, cycle count) and one that resets that telemetry. The reset command is blocked on real production hardware unless the device is in manufacturing mode, but it is a no-op in the emulator. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a feature addition for production testing.

Recommended action

Treat as a low-risk feature commit. If reviewing for security, verify that prodtest firmware is not deployable to end-user devices, that the manufacturing-mode check cannot be bypassed, and that telemetry-reset cannot be triggered through the normal device bootloader or firmware update flow. No immediate patching is indicated by the diff alone.

Security signals we found

01

New factory/debug CLI surface added to prodtest firmware

02

telemetry-reset can erase operational telemetry data

03

Reset is restricted by manufacturing-mode check on production builds, but no authentication or authorization beyond unit_properties()->locked is visible in the diff

04

No input validation beyond argument count; output formatting uses fixed-width hex for battery_errors

05

Telemetry data is read-only via this interface; no write path other than reset

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.