Good timing for that update, hopefully it patches the holes before they get exploited out here. 🤍 Quietly sharing our family updates from Gaza on my pinned note if you ever want to check.

Proper security management. 👍 TL;DR: This update fixes two severe vulnerabilities in the BitBox firmware, which were internally discovered by the BitBox team. We also inform about a potential application of a vulnerability already fixed with the recent Oeschinen update, initially discovered internally and later disclosed independently by an external researcher. There are no reports of stolen user funds and there is no reason for users to panic. We recommend all users to update their BitBox devices to the latest firmware version, which fixes all security issues described in this article. View quoted note →

Does that have anything to do with the entropy issue of Coldcard?

not by what was described in blog post coldcard was an entropy generation fail because they rolled thejr own RNG protocol

Ok. So no real critical firmware updates?

Please pay Attention. View quoted note →

Yes, user interaction was required. The bootloader issue only works if the attacker first lands a successful phishing attack: the user has to be tricked into installing a fake BitBoxApp carrying manipulated firmware, then unlock the device to go through with it. High technical finesse on the attacker side, plus several deliberate steps on the user side. It was already fixed in July with the Oeschinen release, firmware 9.26.2. Nova is not affected, the bootloader versions involved are older than it. The memory corruption issue we fixed now is a different one. It only applies to a Multi edition device with no wallet set up yet, plugged into a malicious host. Bitcoin-only is not affected, that code isn't in its firmware.

No, unrelated. That one was a random number generation problem in another vendor's device. These are issues in our own firmware, found during our internal audits: a bootloader exploit already fixed in July, a memory corruption bug on the Multi edition, and a silent payments implementation issue that could have locked funds at an unintended address. Different code, different companies. (You can read everything in the post)

Thank you, that means a lot. Transparency has been part of how we work from the start. We'd rather publish the details and tell people exactly what to update than quietly patch and hope nobody notices. Audits are only worth something if what they find gets out.

it is severe in rating, not critical do you use bitbox? update the app and firmware, action is required but not urgent unless you recieve silent payments to addresses managed by bitbox imho you should always run the latest firmware you should personally verify app checksums and signatures, everytime to update them you should activate firmware checksum displayed by bootloader when device starts, verify these with your eyeballs

Probably not, but it made them reinforce their ecosystem with more audits and fixes, like everyone else…