Vulnerability in slpjs (CVE-2019-16762)
Summary
Vulnerability in slpjs (CVE-2019-16762). Data can be tampered with by attackers. Mitigation: upgrade to 0.21.4 or later.
Original description
The description as published by the source.
Validator parsing discrepancy due to string encoding
Impact
A specially crafted Bitcoin script can cause a discrepancy between the specified SLP consensus rules and the validation result of the slpjs npm package. An attacker could create a specially crafted Bitcoin script in order to cause a hard-fork from the SLP consensus.
Patches
All versions > 0.21.3 are patched.
Workarounds
Upgrade to any version >= 0.21.4.
References
The bug was located and fixed here.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the slpjs repo
- Email us at info@slp.cash
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2019-16762 has been found in slpjs.
Data can be tampered with by attackers.
What to do: upgrade slpjs to 0.21.4 or later.
If unsure, ask your IT team or search "slpjs CVE-2019-16762" on the vendor's site.
CVE-2019-16762 (slpjs) — CWE-20
Attack vector: remote (network-reachable)
Patched: 0.21.4 — apply immediately
Workaround: Upgrade to any version >= 0.21.4.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in slpjs.
Check the vendor advisory for the affected versions of slpjs.
Severity: ?. Data can be tampered with by attackers.
Update to 0.21.4.
Workaround: Upgrade to any version >= 0.21.4.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'slpjs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'slpjs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
slpjsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Upgrade to any version >= 0.21.4.パッチが適用されるまでの応急処置として、Upgrade to any version >= 0.21.4. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade slpjs to 0.21.4ステージング環境で 0.21.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- web github.com
- web github.com