# CVE-2020-20178: Denial of service in n/a

> Attackers can cause a denial of service in the payout function by creating a large number of account addresses, leading to an exception.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6vwp-x62j-fm2h

## What is CVE-2020-20178?

CVE-2020-20178 is a high-severity denial of service vulnerability in n/a, published on 24 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ethereum 0xe933c0cd9784414d5f278c114904f5a84b396919#code.sol latest version is affected by a denial of service vulnerability in the affected payout function. Once the length of this array is too long, it will result in an exception. Attackers can make attacks by creating a series of account addresses.

## Which versions are affected by CVE-2020-20178?

It affects 1 product.


Products: Whohas Project Whohas.

## How do I fix CVE-2020-20178?

No fix has been published for CVE-2020-20178 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-20178 being exploited?

There is no known exploitation of CVE-2020-20178 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-4258](https://insights.sbomify.com/CVE-2021-4258/): whohas Package Information cleartext transmission (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-20178 and fix it if it is affected.

What it is: CVE-2020-20178 is a high-severity denial of service vulnerability in n/a, published on 24 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-20178 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-20178/ (Markdown: https://insights.sbomify.com/CVE-2020-20178/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-20178
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-20178
- OSV: https://osv.dev/vulnerability/CVE-2020-20178

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-20178/
Summaries are generated and may contain mistakes; the official description above is the record.