{"answers":{"affected":"2 open source packages ship an affected version, including zencashjs.","exploited":"There is no known exploitation of GHSA-xfrc-7mj2-5xh9 in the wild and no public exploit code.","fix":"Upgrade zencashjs to 1.2.0 or later.","what":"GHSA-xfrc-7mj2-5xh9 is a vulnerability in zencashjs, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-xfrc-7mj2-5xh9 and fix it if it is affected.\n\nWhat it is: GHSA-xfrc-7mj2-5xh9 is a vulnerability in zencashjs, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-xfrc-7mj2-5xh9 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zencashjs (npm): affected all versions; fixed in 1.2.0\n- zencashjs (npm): affected all versions; fixed in 1.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-xfrc-7mj2-5xh9/ (Markdown: https://insights.sbomify.com/GHSA-xfrc-7mj2-5xh9/index.md)","id":"GHSA-xfrc-7mj2-5xh9","markdown":"https://insights.sbomify.com/GHSA-xfrc-7mj2-5xh9/index.md","name":"GHSA-xfrc-7mj2-5xh9","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Horizen JavaScript library","requires_auth":"none","summary":"Incorrect address type detection in zencashjs can cause funds sent to specific mainnet P2SH addresses to be lost due to prefix collision with testnet addresses.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.\n\n## Recommendation\n\nUpgrade to version 1.2.0 or later.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Undefined Behavior in zencashjs","id":"GHSA-xfrc-7mj2-5xh9","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"zencashjs","purl":null,"source":"GHSA-xfrc-7mj2-5xh9"},{"ecosystem":"npm","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"zencashjs","purl":"pkg:npm/zencashjs","source":"GHSA-xfrc-7mj2-5xh9"}],"products":null,"published":"2020-09-03","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Incorrect address type detection in zencashjs can cause funds sent to specific mainnet P2SH addresses to be lost due to prefix collision with testnet addresses.","url":"https://insights.sbomify.com/GHSA-xfrc-7mj2-5xh9/"}