Denial of Service (DoS) Affecting github.com/ipfs/go-merkledag package, versions >=0.4.0 <0.8.1

Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper user-input sanitization, such that a ProtoNode can be modified to cause various encode errors which will trigger a panic on common method calls that don't allow for error returns.

These workarounds are available when using impacted versions to avoid panic conditions, and may be generally appropriate in order to provide meaningful feedback to users and avoid generating bad, or unexpected encoded data:

1. Sanitize inputs when allowing user-input to set a new CidBuilder on a ProtoNode.

2. Sanitize Tsize (Link#Size) values such that they are a reasonable byte-size for sub-DAGs where derived from user-input.

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

• GitHub Commit
• GitHub Issue
• GitHub Issue
• GitHub PR
• GitHub PR
• GitHub PR
• GitHub Release