# CVE-2019-11561: Denial of service in n/a

> Attackers can prevent Chuango and compatible burglar alarms from triggering by disrupting sensor state processing, compromising physical security.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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:** 8 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5vw3-x8w8-gf7q

## What is CVE-2019-11561?

CVE-2019-11561 is a medium-severity denial of service vulnerability in n/a, published on 8 May 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 is vulnerable to a Denial of Service attack. When the condition is triggered, the OV2 base station is unable to process sensor states and effectively prevents the alarm from setting off, as demonstrated by Chuango branded products, and non-Chuango branded products such as the Eminent EM8617 OV2 Wifi Alarm System.

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

It affects 10 products.


Products: Chuango A11 Firmware, Chuango A8 Firmware, Chuango Awv Plus Firmware, Chuango B11 Firmware, Chuango Cg-105s Firmware, Chuango G3 Firmware, Chuango G5 Plus Firmware, Chuango G5w 3g Firmware, Chuango G5w Firmware, Chuango H4 Plus Firmware.

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

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

## Is CVE-2019-11561 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11561 is a medium-severity denial of service vulnerability in n/a, published on 8 May 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-11561 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-11561/ (Markdown: https://insights.sbomify.com/CVE-2019-11561/index.md)
```

## Sources

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

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