How severe is GHSA-xfrc-7mj2-5xh9?

No CVSS score has been assigned to GHSA-xfrc-7mj2-5xh9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xfrc-7mj2-5xh9?

GHSA-xfrc-7mj2-5xh9 affects the following packages: zencashjs (npm). Ecosystems affected: npm.

How do I fix GHSA-xfrc-7mj2-5xh9?

Update zencashjs to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xfrc-7mj2-5xh9 is resolved across your whole dependency graph.

How do I detect GHSA-xfrc-7mj2-5xh9 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zencashjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xfrc-7mj2-5xh9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-xfrc-7mj2-5xh9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xfrc-7mj2-5xh9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xfrc-7mj2-5xh9 published, and has it been updated?

GHSA-xfrc-7mj2-5xh9 was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Undefined Behavior in zencashjsGHSA-xfrc-7mj2-5xh9

Fix: ZencashOfficial/zencashjs@db01bd9

GHSA-xfrc-7mj2-5xh9 is a security vulnerability in zencashjs. A fix is available for zencashjs — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

zencashjsnpm

243downloads / week

Description

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.

Recommendation

Upgrade to version 1.2.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`zencashjs`	all versions	1.2.0`npm install zencashjs@1.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zencashjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zencashjs to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xfrc-7mj2-5xh9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 o

O3 Security · Impact-Aware SCA

Is GHSA-xfrc-7mj2-5xh9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works