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

feat(storage,core/embed): support multiple stretched pins in optiga

Public commit record

What the developer wrote

Authored by Ondřej Vejpustek

62/100 · Adequate
feat(storage,core/embed): support multiple stretched pins in optiga

[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 rewrites how the Trezor hardware wallet stores and verifies PINs when the Optiga secure chip is present. It replaces a single 'stretched PIN' slot with a chain of up to 10 slots (currently configured to 1, so behavior is unchanged for users). The goal is to make future brute-force and side-channel attacks against the PIN harder by adding more authorization steps and by separating the HMAC counter reset key from the main unlock path. Because the new code is complex and touches the PIN verification flow, any bug here could affect device security, but the commit itself is a defensive hardening feature rather than a fix for a known vulnerability.

Recommended action

Treat as a high-risk hardening change requiring careful review of the new authorization chain, state clearing, counter-reset logic, and fallback paths. Verify that STRETCHED_PIN_COUNT=1 preserves exact legacy behavior and that enabling values >1 does not introduce bypasses, race conditions, or counter-exhaustion bugs. Run formal/spec-based tests on PIN set/verify/change and firmware downgrade/upgrade scenarios before release.

Security signals we found

01

Refactor of PIN verification and key-derivation path in secure-element code

02

Introduction of chained authorization metadata across multiple Optiga OIDs

03

New encrypted storage key (OPTIGA_HMAC_RESET_KEY) for HMAC counter reset

04

Changes to counter reset values and timing estimates for PIN operations

05

Addition of mpu_reconfig(MPU_MODE_STORAGE) moved earlier in unlock/change_pin entry points

06

No changelog entry and no linked advisory or CVE

Risk score

Why this scored 35/100

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