# CVE-2020-8202: Denial of service in Nextcloud Preferred Providers

> An attacker can cause a denial of service in Nextcloud Preferred Providers by submitting a very long password due to improper input checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5qmp-36gw-8g5g

## What is CVE-2020-8202?

CVE-2020-8202 is a medium-severity denial of service vulnerability in Nextcloud Preferred Providers, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper check of inputs in Nextcloud Preferred Providers app v1.6.0 allowed to perform a denial of service attack when using a very long password.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Nextcloud Preferred Providers.

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

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

## Is CVE-2020-8202 being exploited?

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

## Other vulnerabilities in Nextcloud Preferred Providers

- [CVE-2020-8228](https://insights.sbomify.com/CVE-2020-8228/): Business logic in Nextcloud Preferred Provider (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8202 is a medium-severity denial of service vulnerability in Nextcloud Preferred Providers, published on 30 Jul 2020. 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-8202 in the wild and no public exploit code.

Affected product: Nextcloud Preferred Providers. 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-8202/ (Markdown: https://insights.sbomify.com/CVE-2020-8202/index.md)
```

## Sources

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

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