GHSA-VG44-FW64-CPJX

GHSA-VG44-FW64-CPJX is a high-severity improper authentication vulnerability in eth-ledger-bridge-keyring (npm), affecting versions < 0.2.1. It is fixed in 0.2.1, 0.2.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Incorrect Account Used for Signing

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:

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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

GHSA-VG44-FW64-CPJX has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.2.1, 0.2.2); upgrading removes the vulnerable code path.

Affected versions

eth-ledger-bridge-keyring (< 0.2.1) @metamask/eth-ledger-bridge-keyring (< 0.2.2)

Security releases

eth-ledger-bridge-keyring → 0.2.1 (npm) @metamask/eth-ledger-bridge-keyring → 0.2.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

  1. What is GHSA-VG44-FW64-CPJX? GHSA-VG44-FW64-CPJX is a high-severity improper authentication vulnerability in eth-ledger-bridge-keyring (npm), affecting versions < 0.2.1. It is fixed in 0.2.1, 0.2.2. The application does not adequately verify the identity of a user, device, or process before granting access.
  2. How severe is GHSA-VG44-FW64-CPJX? GHSA-VG44-FW64-CPJX has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by GHSA-VG44-FW64-CPJX?
    • eth-ledger-bridge-keyring (npm) (versions < 0.2.1)
    • @metamask/eth-ledger-bridge-keyring (npm) (versions < 0.2.2)
  4. Is there a fix for GHSA-VG44-FW64-CPJX? Yes. GHSA-VG44-FW64-CPJX is fixed in 0.2.1, 0.2.2. Upgrade to this version or later.
  5. Is GHSA-VG44-FW64-CPJX exploitable, and should I be worried? Whether GHSA-VG44-FW64-CPJX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-VG44-FW64-CPJX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-VG44-FW64-CPJX?
    • Upgrade eth-ledger-bridge-keyring to 0.2.1 or later
    • Upgrade @metamask/eth-ledger-bridge-keyring to 0.2.2 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo