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

simulator: fix factory_randomness

Public commit record

What the developer wrote

Authored by Marko Bencun

58/100 · Thin
simulator: fix factory_randomness

The C simulator still uses the BitBox02 Hal. The newly introduced
factory_randomness method there dereferenced the same static address
as on the device, leading to a segfault.
✓ Descriptive subject✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a crash in the software simulator used for testing the BitBox02 hardware wallet. The simulator was trying to read a special memory address that only exists on the physical device, causing it to crash. The fix makes the simulator return a placeholder value of all zeros instead. This only affects test tooling, not real devices or user funds.

Recommended action

No security action required. This is a test-infrastructure bug fix. Reviewers may want to confirm that the `c-unit-testing` feature is never enabled in production or release firmware builds.

Security signals we found

01

Memory access violation (segfault) in simulator environment

02

Conditional compilation used to separate simulator and device behavior

03

No cryptographic weakness introduced: simulator uses deterministic placeholder randomness, which is appropriate for testing

Risk score

Why this scored 18/100

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