# CVE-2020-28206: Information disclosure in n/a

> Remote attackers can enumerate admin users and brute-force non-admin passwords due to missing rate limits on the login form.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hfhh-3vvv-4gqf

## What is CVE-2020-28206?

CVE-2020-28206 is a medium-severity vulnerability in n/a, published on 2 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Bitrix24 Bitrix Framework (1c site management) 20.0. An "User enumeration and Improper Restriction of Excessive Authentication Attempts" vulnerability exists in the admin login form, allowing a remote user to enumerate users in the administrator group. This also allows brute-force attacks on the passwords of users not in the administrator group.

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

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

It affects 1 product.


Products: Bitrix24 Bitrix Framework.

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

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

## Is CVE-2020-28206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28206 is a medium-severity vulnerability in n/a, published on 2 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28206 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-28206/ (Markdown: https://insights.sbomify.com/CVE-2020-28206/index.md)
```

## Sources

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

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