# CVE-2019-14261: Other in n/a

> Attackers can suppress wireless alarm signals via reactive jamming, bypassing intrusion detection in ABUS Secvest systems.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 3 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jr99-mgvc-mc78

## What is CVE-2019-14261?

CVE-2019-14261 is a high-severity vulnerability in n/a, published on 3 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on ABUS Secvest FUAA50000 3.01.01 devices. Due to an insufficient implementation of jamming detection, an attacker is able to suppress correctly received RF messages sent between wireless peripheral components, e.g., wireless detectors or remote controls, and the ABUS Secvest alarm central. An attacker is able to perform a "reactive jamming" attack. The reactive jamming simply detects the start of a RF message sent by a component of the ABUS Secvest wireless alarm system, for instance a wireless motion detector (FUBW50000) or a remote control (FUBE50014 or FUBE50015), and overlays it with random data before the original RF message ends. Thereby, the receiver (alarm central) is not able to properly decode the original transmitted signal. This enables an attacker to suppress correctly received RF messages of the wireless alarm system in an unauthorized manner, for instance status messages sent by a detector indicating an intrusion.

Weakness: CWE-310

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

It affects 1 product.


Products: Abus Secvest Wireless Alarm System Fuaa50000 Firmware.

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

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

## Is CVE-2019-14261 being exploited?

There is no known exploitation of CVE-2019-14261 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-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-14261 and fix it if it is affected.

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

## Sources

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

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