Advisory

GHSA-3gw4-m5w7-v89c

Also known as: CVE-2020-11090, PYSEC-2020-47

Summary

Uncontrolled Resource Consumption in Indy Node

Details

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.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2020-06-11 00:04 UTC
Modified
2026-08-27 03:56 UTC

Affected packages and fixes

indy-node

PyPI · All systems

Affected

  • introduced 1.12.2, fixed 1.12.3 (ecosystem)

Fixed versions

1.12.3

Fix

  • Fixed version 1.12.3
    pip install --upgrade indy-node==1.12.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences