Skip to content

Uncontrolled Resource Consumption in Indy Node

High severity GitHub Reviewed Published Jun 8, 2020 in hyperledger/indy-node • Updated Sep 23, 2024

Package

pip indy-node (pip)

Affected versions

= 1.12.2

Patched versions

1.12.3

Description

Summary

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.

Discovery

On May 18, Evernym's monitoring of Sovrin StagingNet showed a report of StagingNet losing sufficient consensus to validate write transactions. The problem resolved itself within a few minutes. On May 20th we saw the alert multiple times, and we began analyzing the logs of our steward node. On May 21st we continued to see the alerts with increasing frequency.

It appears that someone is unknowingly sending a malformed transaction, and retrying when the transaction fails. The cause of the errors appear to be the TAA acceptance.

Proposed actions

  • Reproduce problem in integration tests and create a fix
  • Do a hotfix release branching from last stable (current master have some things merged that are too risky)
  • Upgrade BuilderNet, StagingNet and MainNet as soon as possible
  • Improve testing strategy on Indy Node to reduce probability of such bugs

Notes

  • The journalctl logs also show an out-of-memory problem on the Australia node. We need to evaluate if this should be raised as a separate issue.

References

@ryjones ryjones published to hyperledger/indy-node Jun 8, 2020
Reviewed Jun 11, 2020
Published to the GitHub Advisory Database Jun 11, 2020
Last updated Sep 23, 2024

Severity

High

EPSS score

0.171%
(55th percentile)

Weaknesses

CVE ID

CVE-2020-11090

GHSA ID

GHSA-3gw4-m5w7-v89c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.