Vulnerability in indy-node (CVE-2020-11093)
Summary
Vulnerability in indy-node (CVE-2020-11093). Data can be tampered with by attackers. Exploitable via from. Mitigation: upgrade to 1.12.4 or later.
Original description
The description as published by the source.
Hyperledger Indy Node is the server portion of a distributed ledger purpose-built for decentralized identity. In Hyperledger Indy before version 1.12.4, there is lack of signature verification on a specific transaction which enables an attacker to make certain unauthorized alterations to the ledger. Updating a DID with a nym transaction will be written to the ledger if neither ROLE or VERKEY are being changed, regardless of sender. A malicious DID with no particular role can ask an update for another DID (but cannot modify its verkey or role). This is bad because 1) Any DID can write a nym transaction to the ledger (i.e., any DID can spam the ledger with nym transactions), 2) Any DID can change any other DID's alias, 3) The update transaction modifies the ledger metadata associated with a DID.
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-11093 has been found in indy-node.
Attackers can target a specific entry point like from over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade indy-node to 1.12.4 or later.
If unsure, ask your IT team or search "indy-node CVE-2020-11093" on the vendor's site.
CVE-2020-11093 (indy-node) — CWE-347
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: from / V4SGRU86Z58d6TV7PBUe6f / V4SGRU86Z58d6TV7PBUe1a / indy.log
Patched: 1.12.4 — 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-347) exists in indy-node. Attackers reach the vulnerable code path via from without authentication.
Check the vendor advisory for the affected versions of indy-node. Attack surface: from / V4SGRU86Z58d6TV7PBUe6f / V4SGRU86Z58d6TV7PBUe1a / indy.log.
Severity: ?. Data can be tampered with by attackers.
Update to 1.12.4.
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 'indy-node' . 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 'indy-node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
indy-nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade indy-node to 1.12.4ステージング環境で 1.12.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- report github.com
- web github.com