Vulnerability in Hyperledger Indy-Node
CVE-2020-11093
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS 0.012, 68.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Hyperledger Indy-Node — versions < 1.12.4
- Linuxfoundation Indy-Node
Weakness classification (CWE)
References
- github.com/hyperledger/indy-node/security/advisories/GHSA-wh2w-39f4-rpv2 (Exploit, Third Party Advisory)
- github.com/hyperledger/indy-node/blob/master/CHANGELOG.md (Third Party Advisory, Release Notes)
- github.com/hyperledger/indy-node/blob/master/docs/source/auth_rules.md (Third Party Advisory)
- github.com/hyperledger/indy-node/commit/55056f22c83b7c3520488b615e1577e0f895d75a (Patch, Third Party Advisory)