Vulnerability in slpjs (CVE-2020-11071)
Summary
Vulnerability in slpjs (CVE-2020-11071). Data can be tampered with by attackers. Mitigation: upgrade to 0.27.2 or later.
Original description
The description as published by the source.
Impact
Users could experience false-negative validation outcomes for MINT transaction operations. A poorly implemented SLP wallet could allow spending of the affected tokens which would result in the destruction of a user's minting baton.
Patches
npm package slpjs has been patched and published as version 0.27.2.
Workarounds
Upgrade to slpjs 0.27.2.
References
- slpjs commit
For more information
If you have any questions or comments about this advisory:
- Open an issue in slp-validate or slpjs
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-2020-11071 has been found in slpjs.
Data can be tampered with by attackers.
What to do: upgrade slpjs to 0.27.2 or later.
If unsure, ask your IT team or search "slpjs CVE-2020-11071" on the vendor's site.
CVE-2020-11071 (slpjs) — CWE-697
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.27.2 — apply immediately
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-697) exists in slpjs.
Check the vendor advisory for the affected versions of slpjs.
Severity: ?. Data can be tampered with by attackers.
Update to 0.27.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade slpjs to 0.27.2ステージング環境で 0.27.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com