What is GHSA-XFRC-7MJ2-5XH9?

GHSA-XFRC-7MJ2-5XH9 is a critical-severity security vulnerability in zencashjs (npm), affecting versions < 1.2.0. It is fixed in 1.2.0.

Which versions of zencashjs are affected by GHSA-XFRC-7MJ2-5XH9?

zencashjs (npm) versions < 1.2.0 is affected.

Is there a fix for GHSA-XFRC-7MJ2-5XH9?

Yes. GHSA-XFRC-7MJ2-5XH9 is fixed in 1.2.0. Upgrade to this version or later.

Is GHSA-XFRC-7MJ2-5XH9 exploitable, and should I be worried?

Whether GHSA-XFRC-7MJ2-5XH9 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.

What actually determines whether GHSA-XFRC-7MJ2-5XH9 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.

How do I fix GHSA-XFRC-7MJ2-5XH9?

Upgrade zencashjs to 1.2.0 or later.

GHSA-XFRC-7MJ2-5XH9 in zencashjs

Q: Which versions of zencashjs are affected by GHSA-XFRC-7MJ2-5XH9?

zencashjs (npm) versions < 1.2.0 is affected.

Q: Is there a fix for GHSA-XFRC-7MJ2-5XH9?

Yes. GHSA-XFRC-7MJ2-5XH9 is fixed in 1.2.0. Upgrade to this version or later.

Q: Is GHSA-XFRC-7MJ2-5XH9 exploitable, and should I be worried?

Whether GHSA-XFRC-7MJ2-5XH9 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.

Q: What actually determines whether GHSA-XFRC-7MJ2-5XH9 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.

Q: How do I fix GHSA-XFRC-7MJ2-5XH9?

Upgrade zencashjs to 1.2.0 or later.

Summary

Undefined Behavior in zencashjs

Versions of zencashjs prior to 1.2.0 may cause loss of funds when used with cryptocurrency wallets. The package relies on a string comparison of the first two characters of a Horizen address to determine the destination address type of a transaction (P2PKH or P2SH). Due to the base58 address prefixes chosen in Horizen there exists the possibility of a clash of address prefixes for testnet P2PKH and mainnet P2SH addresses, testnet P2PKH addresses start with “zt” while a subset of mainnet P2SH addresses can also start with “zt”. The package interprets transactions sent to a “zt” P2SH address on mainnet as P2PKH transactions erroneously. Any funds sent to a mainnet P2SH multisignature address starting with “zt” will be sent to the wrong address and be lost.

Impact

Affected versions

zencashjs (< 1.2.0)

Security releases

zencashjs → 1.2.0 (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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade to version 1.2.0 or later.

Frequently Asked Questions

What is GHSA-XFRC-7MJ2-5XH9? GHSA-XFRC-7MJ2-5XH9 is a critical-severity security vulnerability in zencashjs (npm), affecting versions < 1.2.0. It is fixed in 1.2.0.
Which versions of zencashjs are affected by GHSA-XFRC-7MJ2-5XH9? zencashjs (npm) versions < 1.2.0 is affected.
Is there a fix for GHSA-XFRC-7MJ2-5XH9? Yes. GHSA-XFRC-7MJ2-5XH9 is fixed in 1.2.0. Upgrade to this version or later.
Is GHSA-XFRC-7MJ2-5XH9 exploitable, and should I be worried? Whether GHSA-XFRC-7MJ2-5XH9 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
What actually determines whether GHSA-XFRC-7MJ2-5XH9 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.
How do I fix GHSA-XFRC-7MJ2-5XH9? Upgrade zencashjs to 1.2.0 or later.