Denial of Service (DoS) Affecting indy-node package, versions [0,]

indy-node is a package that implements server portion of a distributed ledger purpose-built for decentralized identity.

Affected versions of this package are vulnerable to Denial of Service (DoS) when an attacker maxes out the number of client connections allowed by the ledger, leaving the ledger unable to be used for its intended purpose.

The mitigations should be applied to all the individual deployments of Indy, and are not related to a particular release. Any protection against abusive client connections will also prevent the network from 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.

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

• High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

• Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

• Firewall Rules Guidance
• GitHub Commit