# CVE-2019-15913: Weak cryptography in n/a

> Insecure ZigBee key transport allows attackers to steal data, cause denial of service, take over devices, and tamper with messages.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 20 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6mc6-c7f7-5r57

## What is CVE-2019-15913?

CVE-2019-15913 is a critical 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 Xiaomi DGNWG03LM, ZNCZ03LM, MCCGQ01LM, WSDCGQ01LM, RTCGQ01LM devices. Because of insecure key transport in ZigBee communication, causing attackers to gain sensitive information and denial of service attack, take over smart home devices, and tamper with messages.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 5 products.


Products: Mi Dgnwg03lm Firmware, Mi Mccgq01lm Firmware, Mi Rtcgq01lm Firmware, Mi Wsdcgq01lm Firmware, Mi Zncz03lm Firmware.

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

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

## Is CVE-2019-15913 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15914](https://insights.sbomify.com/CVE-2019-15914/): Denial of service in n/a (high 7.5)
- [CVE-2019-15915](https://insights.sbomify.com/CVE-2019-15915/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15913 is a critical 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-15913 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-15913/ (Markdown: https://insights.sbomify.com/CVE-2019-15913/index.md)
```

## Sources

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

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