Trezor Safe improper security check in on-device display
Trezor Safe 3 · Trezor Safe 7 · Trezor Safe 5
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Trezor Safe 3 |
|
|
| Trezor Safe 7 |
|
|
| Trezor Safe 5 |
|
|
Trezor Safe 3 · Trezor Safe 7 · Trezor Safe 5
| Product | Affected | Fixed in |
|---|---|---|
| Trezor Safe 3 |
|
|
| Trezor Safe 7 |
|
|
| Trezor Safe 5 |
|
|
Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum sign_tx / sign_tx_eip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata to a victim then supply a different tail that changes the signed transaction. Fixed in 70c9b0c.
From the CVE record · cisa-cg
A confirmation-binding flaw in the Ethereum sign_tx and sign_tx_eip1559 firmware flows causes the device to confirm only the initial calldata chunk for contract interactions, while signing the full streamed calldata. An attacker who can supply a different calldata tail after presenting the transaction to a victim can change what the victim signs.
Anyone using Trezor Safe 3, Safe 5, or Safe 7 firmware should check whether their firmware includes the fix; affected versions were not specified.