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

feat(core): Add emulator ML-DSA certificates.

Public commit record

What the developer wrote

Authored by Andrew Kozlik

57/100 · Thin
feat(core): Add emulator ML-DSA certificates.
✓ 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 hardcoded test-only cryptographic credentials used by the Trezor emulator (software simulator) for a new ML-DSA device-attestation feature. It does not change real hardware firmware. The credentials are clearly emulator-only placeholders and are not intended for production devices.

Recommended action

No immediate action required. Verify that USE_MCU_ATTESTATION is never enabled in production hardware builds and that these emulator certificates/keys are documented as test-only. Ensure the gen.sh script and placeholder values are not accidentally shipped in production firmware.

Security signals we found

01

Hardcoded cryptographic material (emulator-only certificate and fixed ML-DSA seed)

02

Fixed deterministic secret (memset(dest, 3, SHA256_DIGEST_LENGTH)) used for device authentication in emulator

03

New attestation read/write functions operate on a static in-memory buffer with bounds checks

04

Code is guarded by USE_MCU_ATTESTATION and TREZOR_MODEL_T3W1 macros, limiting scope

Risk score

Why this scored 18/100

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