# CVE-2019-9861: Security feature bypass in n/a

> Attackers can clone RFID keys to bypass security and deactivate the alarm system due to insecure MIFARE Classic technology.

- **Severity:** High 8.1 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mjxp-pfh5-29xr

## What is CVE-2019-9861?

CVE-2019-9861 is a high-severity vulnerability in n/a, published on 14 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Due to the use of an insecure RFID technology (MIFARE Classic), ABUS proximity chip keys (RFID tokens) of the ABUS Secvest FUAA50000 wireless alarm system can easily be cloned and used to deactivate the alarm system in an unauthorized way.

Weakness: CWE-310

## Which versions are affected by CVE-2019-9861?

It affects 1 product.


Products: Abus Secvest Wireless Alarm System Fuaa50000 Firmware.

## How do I fix CVE-2019-9861?

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

## Is CVE-2019-9861 being exploited?

There is no known exploitation of CVE-2019-9861 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-2020-28973](https://insights.sbomify.com/CVE-2020-28973/): Auth bypass in n/a (high 7.5)
- [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-2019-9861 and fix it if it is affected.

What it is: CVE-2019-9861 is a high-severity vulnerability in n/a, published on 14 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9861 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-2019-9861/ (Markdown: https://insights.sbomify.com/CVE-2019-9861/index.md)
```

## Sources

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

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