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

simulator-graphical: fix factory_randomness

Public commit record

What the developer wrote

Authored by Marko Bencun

50/100 · Thin
simulator-graphical: fix factory_randomness

Same as cee5bdb3ba06f60b93213f9c2a183a7683fe1551, but for BB02
graphical simulator.
✓ Descriptive subject✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit fixes a simulator-only bug where the graphical BitBox02 simulator was accidentally using real device randomness instead of the fixed test value used by other simulators/test builds. The change makes the graphical simulator use the same predictable 'factory randomness' as the C unit-testing simulator. This is a test/simulator hardening fix, not a fix for the real hardware wallet firmware.

Recommended action

No urgent action for end users; this change only affects simulator/test builds. Developers should ensure simulator builds consistently use stubbed randomness and that production firmware remains excluded from the changed cfg guards.

Security signals we found

01

Use of fixed/zero 'randomness' in simulator/test code paths

02

Conditional compilation feature flag change

03

Reference to a prior similar fix for another simulator variant

04

No change to production firmware code paths

Risk score

Why this scored 33/100

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