Patchfirst
CVE-2020-11090 High · 7.5 EPSS 2.2%

Uncontrolled Resource Consumption in Indy Node

Hyperledger · Indy Node

Official description · CVE.org

In Indy Node 1.12.2, there is an Uncontrolled Resource Consumption vulnerability. Indy Node has a bug in TAA handling code. The current primary can be crashed with a malformed transaction from a client, which leads to a view change. Repeated rapid view changes have the potential of bringing down the network. This is fixed in version 1.12.3.

Breakdown
21.7 / 100
Exploited
Not confirmed
Reports
0
Tactics
1/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. What they do

Disclosed on 11 Jun 2020. No public exploit code or confirmed exploitation is recorded.

4 fixes in indy-node over 2 years. The latest fix listed for indy-node is 1.13.0.dev2.

Fixes in indy-nodePyPI package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 1.12.3CVE-2020-1109011 Jun 2020
  2. 1.12.4CVE-2020-1109324 Dec 2020
  3. 1.12.5rc1CVE-2022-310206 Sep 2022
  4. 1.13.0.dev2CVE-2022-310069 Sep 2022Latest listed

techniques

1 , grouped by in kill-chain order 1

ImpactTA0040

MITRE CTID mapping of the CVE · primary impact

Detection

0 rules for this CVE · 3 general rules for its techniques

Rules for this CVE

0 that reference CVE-2020-11090 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

General rules for this CVE’s techniques

These detect the technique in general, not this specific vulnerability.

Application or System ExploitationT1499.0043 general rules

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: indy-node.

Upgrade to 1.12.3 or later

pippip install "indy-node>=1.12.3"

The first fix for CVE-2020-11090. No other CVE tracked by Patchfirst affects this package.

Affected versions

If you runUpgrade to
All versions before 1.12.31.12.3

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

References

3 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close