CVE-2020-11090 – indy-node

Package

Manager: pip
Name: indy-node
Vulnerable Version: =1.12.2 || >=1.12.2 <1.12.3

Severity

Level: Critical

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS: 0.00408 pctl0.6051

Details

Uncontrolled Resource Consumption in Indy Node # 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.

Metadata

Created: 2020-06-11T00:04:15Z
Modified: 2024-11-18T16:26:06Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/06/GHSA-3gw4-m5w7-v89c/GHSA-3gw4-m5w7-v89c.json
CWE IDs: ["CWE-400"]
Alternative ID: GHSA-3gw4-m5w7-v89c
Finding: F067
Auto approve: 1