CVE-2020-11093
No exploitation reported by the sources we read.
- Published2020-12-24
- Fixed in1.12.4
- WeaknessCWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2020-12-2420:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.12 | < 1.12.4 | 1.12.4 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Linuxfoundation indy-node to 1.12.4
Advisories and patches
- github.comRelease Notes
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.17.5known since 2026-10-23
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-347known since 2026-10-23
- FIRST EPSSEPSS score1.2 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2024-08-30
Identifiers
- EUVD-2020-0088same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-wh2w-39f4-rpv2same flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2020-48same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2020-12-24
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-wh2w-39f4-rpv2
Frequently asked questions
What is CVE-2020-11093?
Is CVE-2020-11093 actively exploited?
What is the CVSS score for CVE-2020-11093?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-wh2w-39f4-rpv2
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served