CVE-2022-31006: Hyperledger indy-node vulnerable to denial of service

CVE-2022-31006 · Severity: low · CVSS 3.1 · Published 2022-09-09

indy-node is the server portion of Hyperledger Indy, a distributed ledger purpose-built for decentralized identity. In vulnerable versions of indy-node, an attacker can max out the number of client connections allowed by the ledger, leaving the ledger unable to be used for its intended purpose. However, the ledger content will not be impacted and the ledger will resume functioning after the attack. This attack exploits the trade-off between resilience and availability. Any protection against abusive client connections will also prevent the network being accessed by certain legitimate users. As a result, validator nodes must tune their firewall rules to ensure the right trade-off for their network's expected users. The guidance to network operators for the use of firewall rules in the deployment of Indy networks has been modified to better protect against denial of service attacks by increasing the cost and complexity in mounting such attacks. The mitigation for this vulnerability is not in the Hyperledger Indy code per se, but rather in the individual deployments of Indy. The mitigations should be applied to all deployments of Indy, and are not related to a particular release.

Technologies: indy-node (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2022-31006 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-31006 being exploited in the wild.
How severe is CVE-2022-31006?
Low severity, with a CVSS score of 3.1, published 9 September 2022.
Which products and versions are affected?
indy-node (PyPI) ECOSYSTEM:introduced=0,last_affected=1.12.6, GIT:introduced=0,fixed=53a2a1bf1a26cb8ba710fd6adc8bcf275186a4b3|ECOSYSTEM:introduced=0,fixed=1.13.0.dev2.
Is there a fix for CVE-2022-31006?
Yes. indy-node (PyPI): upgrade to 1.13.0.dev2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-31006?
Check whether you run indy-node (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • indy-node (PyPI): upgrade to 1.13.0.dev2 or later
    pip install "indy-node>=1.13.0.dev2"

Affected products

  • indy-node (PyPI) ECOSYSTEM:introduced=0,last_affected=1.12.6, GIT:introduced=0,fixed=53a2a1bf1a26cb8ba710fd6adc8bcf275186a4b3|ECOSYSTEM:introduced=0,fixed=1.13.0.dev2

Identifiers

  • CVE-2022-31006
  • GHSA-x996-7qh9-7ff7
  • PYSEC-2022-270

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.