# CVE-2019-9862: Information disclosure in n/a

> Attackers can eavesdrop on cleartext wireless signals to steal sensitive data like rolling codes from ABUS Secvest alarm systems.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6jm4-cmgj-f6fh

## What is CVE-2019-9862?

CVE-2019-9862 is a medium-severity vulnerability in n/a, published on 27 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on ABUS Secvest wireless alarm system FUAA50000 3.01.01 in conjunction with Secvest remote control FUBE50014 or FUBE50015. Because "encrypted signal transmission" is missing, an attacker is able to eavesdrop sensitive data as cleartext (for instance, the current rolling code state).

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 3 products.


Products: Abus Secvest Wireless Alarm System Fuaa50000 Firmware, Abus Secvest Wireless Remote Control Fube50014 Firmware, Abus Secvest Wireless Remote Control Fube50015 Firmware.

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

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

## Is CVE-2019-9862 being exploited?

There is no known exploitation of CVE-2019-9862 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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9862 and fix it if it is affected.

What it is: CVE-2019-9862 is a medium-severity vulnerability in n/a, published on 27 Mar 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-9862 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-9862/ (Markdown: https://insights.sbomify.com/CVE-2019-9862/index.md)
```

## Sources

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

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