Incorrect Account Used for Signing
Impact
Anybody using this library to sign with a BIP44 account other than the first account may be affected. If a user is signing with the first account (i.e. the account at index 0), or with the legacy MEW/MyCrypto HD path, they are not affected.
The vulnerability impacts cases where the user signs a personal message or transaction without first adding the account. This includes cases where the user has already added the account in a previous session (i.e. they added the account, reset the application, then signed something). The serialization/deserialization process does restore a previously added account, but it doesn't restore the index instructing the keyring to use that account for signing. As a result, after serializing then deserializing the keyring state, the account at index 0 is always used for signing even if it isn't the current account.
Patches
This has been patched (#14) in version >=0.2.1 of eth-ledger-bridge-keyring, and in version >=0.2.2 of @metamask/eth-ledger-bridge-keyring. Users are encouraged to migrate to the new package name.
Workarounds
To work around this problem without updating, you should remove then re-add the account before use. As long as the account was added during the lifetime of that process, signing with that account should work correctly.
For more information
If you have any questions or comments about this advisory:
- Open an issue in MetaMask/eth-ledger-bridge-keyring on GitHub
- Email the MetaMask team at hello@metamask.io
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | eth-ledger-bridge-keyring | < 0.2.1 | 0.2.1 |
| Paquete de npm | @metamask/eth-ledger-bridge-keyring | < 0.2.2 | 0.2.2 |
Referencias
- https://github.com/MetaMask/eth-ledger-bridge-keyring/security/advisories/GHSA-vg44-fw64-cpjx
- https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/14
- https://github.com/MetaMask/eth-ledger-bridge-keyring/commit/f32e529d13a53e55f558d903534d631846dc26ce
- https://github.com/advisories/GHSA-vg44-fw64-cpjx
- https://snyk.io/vuln/SNYK-JS-ETHLEDGERBRIDGEKEYRING-561121
- https://www.npmjs.com/advisories/1497
- https://www.npmjs.com/advisories/1498
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H- Debilidad (CWE)
CWE-287- Plataforma
- npm
- Paquete
eth-ledger-bridge-keyring, @metamask/eth-ledger-bridge-keyring- Publicada
- 24.03.2020
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-vg44-fw64-cpjx - CC BY 4.0
Historial de vulnerabilidades: eth-ledger-bridge-keyring
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
Esta es la única vulnerabilidad conocida de este paquete.
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.