# CVE-2020-8228: Business logic in Nextcloud Preferred Provider

> Missing rate limiting in Nextcloud Preferred Provider allows attackers to brute-force passwords, potentially leading to account takeover.

- **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:** Yes
- **Published:** 5 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rwr6-pc6f-m2cc

## What is CVE-2020-8228?

CVE-2020-8228 is a medium-severity vulnerability in Opensuse Backports Sle, published on 5 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing rate limit in the Preferred Providers app 1.7.0 allowed an attacker to set the password an uncontrolled amount of times.

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

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

It affects 3 products.


Products: Nextcloud Preferred Providers, Opensuse Backports Sle, Opensuse Leap.

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

Apply the vendor's patch.

## Is CVE-2020-8228 being exploited?

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

## Other vulnerabilities in Opensuse Backports Sle

- [CVE-2020-8202](https://insights.sbomify.com/CVE-2020-8202/): Denial of service in Nextcloud Preferred Providers (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8228 is a medium-severity vulnerability in Opensuse Backports Sle, published on 5 Oct 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-8228 in the wild and no public exploit code.

Affected product: Opensuse Backports Sle. 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-8228/ (Markdown: https://insights.sbomify.com/CVE-2020-8228/index.md)
```

## Sources

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

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