# CVE-2020-28973: Auth bypass in n/a

> Attackers can bypass authentication on the ABUS Secvest alarm system to steal credentials and disable the security system.

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

## What is CVE-2020-28973?

CVE-2020-28973 is a high-severity authentication bypass vulnerability in n/a, published on 21 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ABUS Secvest wireless alarm system FUAA50000 (v3.01.17) fails to properly authenticate some requests to its built-in HTTPS interface. Someone can use this vulnerability to obtain sensitive information from the system, such as usernames and passwords. This information can then be used to reconfigure or disable the alarm system.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Abus Secvest Wireless Alarm System Fuaa50000 Firmware.

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

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

## Is CVE-2020-28973 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9863](https://insights.sbomify.com/CVE-2019-9863/): Weak cryptography in n/a (critical 9.8)
- [CVE-2019-9861](https://insights.sbomify.com/CVE-2019-9861/): Security feature bypass in n/a (high 8.1)
- [CVE-2019-14261](https://insights.sbomify.com/CVE-2019-14261/): Other in n/a (high 7.5)
- [CVE-2019-9860](https://insights.sbomify.com/CVE-2019-9860/): Weak cryptography in n/a (high 7.5)
- [CVE-2019-9862](https://insights.sbomify.com/CVE-2019-9862/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28973 is a high-severity authentication bypass vulnerability in n/a, published on 21 Apr 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-28973 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-28973/ (Markdown: https://insights.sbomify.com/CVE-2020-28973/index.md)
```

## Sources

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

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