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

> Attackers can cause a denial of service on ASUS ZigBee devices by exploiting the network discovery procedure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 20 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qrrp-pg2q-h56f

## What is CVE-2019-15910?

CVE-2019-15910 is a high-severity denial of service vulnerability in n/a, published on 20 Dec 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 ASUS HG100, MW100, WS-101, TS-101, AS-101, MS-101, DL-101 devices using ZigBee PRO. Attackers can utilize the "discover ZigBee network procedure" to perform a denial of service attack.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 7 products.


Products: Asus As-101 Firmware, Asus Dl-101 Firmware, Asus Hg100 Firmware, Asus Ms-101 Firmware, Asus Mw100 Firmware, Asus Ts-101 Firmware, Asus Ws-101 Firmware.

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

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

## Is CVE-2019-15910 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15911](https://insights.sbomify.com/CVE-2019-15911/): Weak cryptography in n/a (critical 9.8)
- [CVE-2019-15912](https://insights.sbomify.com/CVE-2019-15912/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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