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

> Attackers can bypass alarm security by replaying static RF codes to arm, disarm, or trigger burglar alarms remotely.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9c2v-c4r3-gwmm

## What is CVE-2019-9659?

CVE-2019-9659 is a critical vulnerability in n/a, published on 11 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Chuango 433 MHz burglar-alarm product line uses static codes in the RF remote control, allowing an attacker to arm, disarm, or trigger the alarm remotely via replay attacks, as demonstrated by Chuango branded products, and non-Chuango branded products such as the Eminent EM8617 OV2 Wifi Alarm System.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 11 products.


Products: Chuango A11 Pstn\/Lcd\/Rfid Touch Alarm System Firmware, Chuango A8 Pstn Alarm System Firmware, Chuango Awv Plus Wifi Alarm System Firmware, Chuango B11 Dual-Network Alarm System Firmware, Chuango Cg-105s On-Site Alarm System Firmware, Chuango G3 Gsm\/Sms Alarm System Firmware, Chuango G5 Plus Gsm\/Sms\/Rfid Touch Alarm System Firmware, Chuango G5w 3g Firmware, Chuango Wifi\/Cellular Smart Home System H4 Plus Firmware, Chuango Wifi Alarm System Firmware, Eminent Em8617 Ov2 Wifi Alarm System Firmware.

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

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

## Is CVE-2019-9659 being exploited?

There is no known exploitation of CVE-2019-9659 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

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

## Sources

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

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