Read the docs
TI-2020-19662 Aliases GHSA-xfrc-7mj2-5xh9

Undefined Behavior in zencashjs

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

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.

Why it matters now

Fix Fixed zencashjs (npm): 1.2.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—zencashjs (npm)before 1.2.01.2.0Patch availableGHSA-xfrc-7mj2-5xh9
  • zencashjs (npm) Vendor— Affected before 1.2.0 Fixed in 1.2.0 Patch available GHSA-xfrc-7mj2-5xh9

Remediation

  • Fix · GHSA-xfrc-7mj2-5xh9 zencashjs (npm) Fixed in 1.2.0 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-xfrc-7mj2-5xh9

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences