CVE-2020-11090: Uncontrolled Resource Consumption in indy-node

indy-node Updated 02 Oct 2025

Summary

11/06/2020
Yes i
Critical
7.5

CVE-2020-11090: In Indy Node 1.12.2, there is an Uncontrolled Resource Consumption vulnerability. Affects indy-node versions < 1.12.3. Fixed in 1.12.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Indy Node is a package available on PyPI that is used for building distributed ledger solutions. It provides a set of tools and libraries for creating and managing a decentralized identity ecosystem. Indy Node is vulnerable to an Uncontrolled Resource Consumption issue in its TAA (Transaction Author Agreement) handling code. This vulnerability allows a malicious client to crash the current primary node by sending a malformed transaction, leading to a view change. Rapid view changes can potentially disrupt the entire network.

Vulnerability Detail

The Uncontrolled Resource Consumption vulnerability in Indy Node arises from a bug in its TAA handling code. By exploiting this vulnerability, an attacker can send a specially crafted transaction to the primary node, causing it to crash and trigger a view change. This can be done repeatedly and rapidly, potentially leading to a denial-of-service (DoS) situation where the network becomes unavailable. The vulnerability has been assigned the CVE identifier CVE-2020-11090 and has been fixed in version 1.12.3 of Indy Node.

How To Fix

Minimum fixed version

1.12.3

This is the first release that contains the fix.

pip install --upgrade "indy-node==1.12.3"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to upgrade to the fixed version of Indy Node as soon as possible.

Conclusion

The Uncontrolled Resource Consumption vulnerability in Indy Node can be exploited by a malicious client to crash the primary node and potentially disrupt the entire network. It is crucial to upgrade to version 1.12.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for indy-node →

Share this vulnerability

FAQ

Indy Node is a package used for building distributed ledger solutions and managing decentralized identity ecosystems.

The vulnerability allows a malicious client to crash the primary node and potentially disrupt the entire network.

You can fix this vulnerability by upgrading to version 1.12.3 or later of Indy Node.

No, there is no known workaround for this vulnerability.

Yes, the vulnerability has been assigned the CVE identifier CVE-2020-11090.

Related vulnerabilities

Recent vulnerabilities recorded for indy-node.

How To Fix

Minimum fixed version

1.12.3

This is the first release that contains the fix.

pip install --upgrade "indy-node==1.12.3"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback