[Bug]: Double transactions triggered on Ledger Device

[nikolay44u]

Describe the bug

After the latest update, Metamask extension seems to be trigerring a second transaction on Ledger hardware devices, after the first one has been manually approved on the Ledger device.

Workflow: On a dapp, I trigger a transaction, and approve it on the Metamask extension, and then finally approve it on Ledger HW and it gets broadcasted to the network. This should be the end of the transaction. However, after few seconds, the Ledger shows the same transaction again for approval with the same nonce.

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

1. On a dapp, I trigger a transaction.
2. Approve it on the Metamask extension,
3. And then finally approve it on Ledger HW and the TX gets broadcasted to the network.

This should be the end of the transaction.

However, after few seconds, the Ledger shows the same transaction again for approval with the same nonce.

Error messages or log output

No response

Version

11.14.3

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

Ledger

Additional context

No response

Severity

Critical - tried on multiple devices

[vivek-consensys]

@nikolay44u can you please share what firmware version you are using on the Ledger device? Also, which Ledger device you are using?

[gauthierpetetin]

Hi @MetaMask/hardware-wallets , I added a sev2 label for now but feel free to re-assess and turn this into a sev1 if needed.

[nikolay44u]

@nikolay44u can you please share what firmware version you are using on the Ledger device? Also, which Ledger device you are using?

The Ledger Firmware version(updated to the latest version) is:
Secure Element 2.1.0
Microcontroller: 1.12

[vivek-consensys]

@nikolay44u can you please share what firmware version you are using on the Ledger device? Also, which Ledger device you are using?

The Ledger Firmware version(updated to the latest version) is: Secure Element 2.1.0 Microcontroller: 1.12

hi @nikolay44u , please update your firmware versions. I was not able to reproduce this issue using the following versions on Ledger Nano X:-

Secure Element - 2.2.3
Microcontroller - 2.30
Bootloader - 1.16

[nikolay44u]

@nikolay44u can you please share what firmware version you are using on the Ledger device? Also, which Ledger device you are using?

The Ledger Firmware version(updated to the latest version) is: Secure Element 2.1.0 Microcontroller: 1.12

hi @nikolay44u , please update your firmware versions. I was not able to reproduce this issue using the following versions on Ledger Nano X:-

Secure Element - 2.2.3 Microcontroller - 2.30 Bootloader - 1.16

Im on the latest firmware as per Ledger Live. The app is also up-to date.

My device is Ledger Nano S. Havent tried on the X yet.

It keeps happening on ETH network. Havent had this issue on another L2 network yet.

Same flow as outlined earlier - tx that was already approved on the Hw device, appears again for approval on the Hw device. I just now had to cancel one such tx on the device because it was already confirmed onchain 😅

[angelcheung22]

Pending support from Ledger team with nano s device. Issue cannot be reproduced from hardware wallet team on both nano X and nano S plus specific. Putting this to blocked.