# CVE-2020-8827: Improper Restriction of Excessive Authentication Attempts in Argo API

> Attackers can brute-force credentials due to missing rate limiting and lockout mechanisms in the Argo CD API.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-argo-cd-2020-8827, GHSA-xcqr-9h24-vrgw, GO-2022-0892

## What is CVE-2020-8827?

CVE-2020-8827 is a high-severity vulnerability in Argoproj Argo Cd, published on 8 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

As of v1.5.0, the Argo API does not implement anti-automation measures such as rate limiting, account lockouts, or other anti-bruteforce measures. Attackers can submit an unlimited number of authentication attempts without consequence.

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

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

4 open source packages ship an affected version, including github.com/argoproj/argo-cd and argo-cd. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-cd` | Go | All versions | 1.5.1 |
| `github.com/argoproj/argo-cd` | Go | All versions | 1.5.1 |
| `github.com/argoproj/argo-cd` | Go | All versions | 1.5.1 |
| `argo-cd` | Bitnami | All versions | 1.5.0 |

Products: Argoproj Argo Cd.

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

Upgrade github.com/argoproj/argo-cd to 1.5.1 or later.

## Is CVE-2020-8827 being exploited?

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

## Other vulnerabilities in Argoproj Argo Cd

- [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0)
- [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0)
- [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9)
- [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9)
- [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8827 is a high-severity vulnerability in Argoproj Argo Cd, published on 8 Apr 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-8827 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-cd (Go): affected all versions; fixed in 1.5.1
- github.com/argoproj/argo-cd (Go): affected all versions; fixed in 1.5.1
- github.com/argoproj/argo-cd (Go): affected all versions; fixed in 1.5.1
- argo-cd (Bitnami): affected all versions; fixed in 1.5.0

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-8827/ (Markdown: https://insights.sbomify.com/CVE-2020-8827/index.md)
```

## Sources

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

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