# CVE-2018-25029: Security feature bypass in Z-Wave

> Attackers can downgrade Z-Wave security during pairing to intercept and spoof traffic, affecting IoT devices using Silicon Labs Z-Wave.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v7cj-26wg-65rw

## What is CVE-2018-25029?

CVE-2018-25029 is a high-severity vulnerability in Silicon Labs Z-Wave, published on 4 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Z-Wave specification requires that S2 security can be downgraded to S0 or other less secure protocols, allowing an attacker within radio range during pairing to downgrade and then exploit a different vulnerability (CVE-2013-20003) to intercept and spoof traffic.

Weakness: CWE-757 (Selection of Less-Secure Algorithm During Negotiation)

## Which versions are affected by CVE-2018-25029?

It affects 5 products.


Products: Silabs Zgm130s037hgn Firmware, Silabs Zgm2305a27hgn Firmware, Silabs Zgm230sb27hgn Firmware, Silabs Zm5101 Firmware, Silabs Zm5202 Firmware.

## How do I fix CVE-2018-25029?

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

## Is CVE-2018-25029 being exploited?

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

## Other vulnerabilities in Silicon Labs Z-Wave

- [CVE-2013-20003](https://insights.sbomify.com/CVE-2013-20003/): Weak cryptography in Z-Wave (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25029 and fix it if it is affected.

What it is: CVE-2018-25029 is a high-severity vulnerability in Silicon Labs Z-Wave, published on 4 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25029 in the wild and no public exploit code.

Affected product: Silicon Labs Z-Wave. 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-2018-25029/ (Markdown: https://insights.sbomify.com/CVE-2018-25029/index.md)
```

## Sources

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

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